openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandro Colorado <...@oooes.org>
Subject Re: Moving code from oooforum to mwiki
Date Tue, 17 Feb 2015 21:58:28 GMT
On Tue, Feb 17, 2015 at 4:50 PM, Dennis E. Hamilton <dennis.hamilton@acm.org
> wrote:

> It seems to me that the mwiki is the best place, based on the origin of
> whatever the code examples are.  Putting it on the SVN of the code repro is
> inappropriate because of license requirements.  Putting it on the web site
> is more work.
>
> Do we know who the original contributors are for these, and can we
> preserve their attribution?
>

​No DannyB has been off the radar for 10+ years.​



>
>  - Dennis
>
> -----Original Message-----
> From: acolorado@gmail.com [mailto:acolorado@gmail.com] On Behalf Of
> Alexandro Colorado
> Sent: Tuesday, February 17, 2015 12:24
> To: dev
> Subject: Re: Moving code from oooforum to mwiki
>
> On Tue, Feb 17, 2015 at 3:17 PM, Marcus <marcus.mail@wtnet.de> wrote:
>
> > Am 02/17/2015 08:56 PM, schrieb Alexandro Colorado:
> >
> >> Is more than code, there is an explanation and tutorials going into each
> >> code. Also these files are not indivdiual so you need to reference to
> >> other
> >> pieces of code to being able to run.
> >>
> >
> > even then it would be in good hands in SVN. The AOO code is also splitup
> > into many different files resp. file types. And only when they work
> > together we get a run-able binary at the end.
> >
>
> ​I didn't mean refferenced as depencencies, I meant referenced as in 'how
> to run' this piece of code. This could only be added as comments on code
> which becomes a bit of a hassle when you dealing with multiple files.​
>
> ​​
>
>
> >
> > Marcus
> >
> >
> >
> >  On Tue, Feb 17, 2015 at 2:53 PM, jan i<jani@apache.org>  wrote:
> >>
> >>  On Tuesday, February 17, 2015, Alexandro Colorado<jza@oooes.org>
> wrote:
> >>>
> >>>  Just to inform the community that works with Python, I am in the
> process
> >>>>
> >>> of
> >>>
> >>>> moving some of the relevant code that used to be hosted on oooforum.
> >>>>
> >>> Since
> >>>
> >>>> the past issues with that forum I am copy-pasting the code to the
> mwiki
> >>>>
> >>> so
> >>>
> >>>> it can be hosted so in case oooforum goes away forever, these code can
> >>>> still be survived and reused.
> >>>>
> >>>> Same is going with other sites and tutorials. I encourage people that
> >>>>
> >>> want
> >>>
> >>>> to contribute with this efforts, or want to review and maybe update
> this
> >>>> code since its pretty old and might not be useful with the current
> >>>>
> >>> versions
> >>>
> >>>> of PyUNO.
> >>>>
> >>>
> >>>
> >>> Would it not be better to put it in svn?
> >>>
> >>> rgds
> >>> jan i
> >>>
> >>>
> >>>> Links are here:
> >>>> https://wiki.openoffice.org/wiki/Python
> >>>>
> >>>> Primarily on PyUNO Modules.
> >>>>
> >>>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
> >
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> 882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>


-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message