From: Paul T. <pau...@gm...> - 2011-11-25 18:10:57
|
With berlios no longer hosting projects, any thoughts on where docutils is going to migrate to? Paul |
From: Guenter M. <mi...@us...> - 2011-11-25 19:50:18
|
On 2011-11-25, Paul Tremblay wrote: > With berlios no longer hosting projects, any thoughts on where docutils is > going to migrate to? As * using berlios for the repo was only done because sourceforge did not offer SVN at this time and * SVN is supported by sourceforge for some years now, moving the repo to sourceforge seems the "minimal invasive" choice. (Someone has to do it, though.) Günter |
From: engelbert g. <eng...@gm...> - 2011-11-27 19:21:27
|
plan * revoke all write grants to berlios * svnadmin dump on berlios * import into sf svn is it that simple ? -- engelbert On Fri, Nov 25, 2011 at 8:46 PM, Guenter Milde <mi...@us...> wrote: > On 2011-11-25, Paul Tremblay wrote: > >> With berlios no longer hosting projects, any thoughts on where docutils is >> going to migrate to? > > As > > * using berlios for the repo was only done because sourceforge did not > offer SVN at this time and > > * SVN is supported by sourceforge for some years now, > > moving the repo to sourceforge seems the "minimal invasive" choice. > > > (Someone has to do it, though.) > > Günter > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Docutils-develop mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-develop > > Please use "Reply All" to reply to the list. > -- http://darefoot.blogspot.com |
From: Paul T. <pau...@gm...> - 2011-11-25 22:33:06
|
On 11/25/11 2:46 PM, Guenter Milde wrote: > On 2011-11-25, Paul Tremblay wrote: > >> With berlios no longer hosting projects, any thoughts on where docutils is >> going to migrate to? > As > > * using berlios for the repo was only done because sourceforge did not > offer SVN at this time and > > * SVN is supported by sourceforge for some years now, > > moving the repo to sourceforge seems the "minimal invasive" choice. > > > (Someone has to do it, though.) > > That sounds logical. When I did a search on line, I found that bitbucket and github seem to be all the rage, and no one is using sourceforge. I just wondered if I am missing something. Paul |
From: Fred D. <fr...@fd...> - 2011-11-25 23:27:24
|
On Fri, Nov 25, 2011 at 5:32 PM, Paul Tremblay <pau...@gm...> wrote: > When I did a search on line, I found that bitbucket > and github seem to be all the rage, and no one is using sourceforge. I > just wondered if I am missing something. I think SourceForge has been bypassed for new projects since many didn't really like their tracker, and sticking with CVS for so long was a mistake on their part. Since then, I think their status was pretty well set. We just don't hear about them much any more. -Fred -- Fred L. Drake, Jr. <fred at fdrake.net> "A storm broke loose in my mind." --Albert Einstein |
From: Matthew B. <mat...@gm...> - 2011-11-26 18:52:09
|
Hi, On Fri, Nov 25, 2011 at 3:26 PM, Fred Drake <fr...@fd...> wrote: > On Fri, Nov 25, 2011 at 5:32 PM, Paul Tremblay <pau...@gm...> wrote: >> When I did a search on line, I found that bitbucket >> and github seem to be all the rage, and no one is using sourceforge. I >> just wondered if I am missing something. > > I think SourceForge has been bypassed for new projects since many > didn't really like their tracker, and sticking with CVS for so long > was a mistake on their part. > > Since then, I think their status was pretty well set. We just don't > hear about them much any more. Also a lot of projects are switching to distributed version control (mercurial -> bitbucket, git -> github) http://www.joelonsoftware.com/items/2010/03/17.html Best, Matthew |
From: Ben F. <ben...@be...> - 2011-11-26 21:04:38
|
Matthew Brett <mat...@gm...> writes: > Hi, > > On Fri, Nov 25, 2011 at 3:26 PM, Fred Drake <fr...@fd...> wrote: > > I think SourceForge has been bypassed for new projects since many > > didn't really like their tracker, and sticking with CVS for so long > > was a mistake on their part. > > Also a lot of projects are switching to distributed version control > (mercurial -> bitbucket, git -> github) Note that Sourceforge has DVCS hosting for projects since 2009 <URL:http://sourceforge.net/apps/trac/sourceforge/wiki/Bazaar> <URL:http://sourceforge.net/apps/trac/sourceforge/wiki/Mercurial>. -- \ “The number of UNIX installations has grown to 10, with more | `\ expected.” —Unix Programmer's Manual, 2nd Ed., 1972-06-12 | _o__) | Ben Finney |
From: Matthew B. <mat...@gm...> - 2011-11-26 22:19:29
|
Hi, On Sat, Nov 26, 2011 at 1:04 PM, Ben Finney <ben...@be...> wrote: > Matthew Brett <mat...@gm...> writes: > >> Hi, >> >> On Fri, Nov 25, 2011 at 3:26 PM, Fred Drake <fr...@fd...> wrote: >> > I think SourceForge has been bypassed for new projects since many >> > didn't really like their tracker, and sticking with CVS for so long >> > was a mistake on their part. >> >> Also a lot of projects are switching to distributed version control >> (mercurial -> bitbucket, git -> github) > > Note that Sourceforge has DVCS hosting for projects since 2009 > <URL:http://sourceforge.net/apps/trac/sourceforge/wiki/Bazaar> > <URL:http://sourceforge.net/apps/trac/sourceforge/wiki/Mercurial>. Right - sourceforge do git too [1]. My impression (uninformed by data) is that users of mercurial have preferred the code interfaces of bitbucket or google code [2], and users of git vastly prefer github. Obviously bitbucket or github aren't going to be of much interest if you're sticking with subversion. Best, Matthew [1] http://sourceforge.net/apps/trac/sourceforge/wiki/Git [2] http://nipyworld.blogspot.com/2011/07/why-you-shouldnt-use-google-code.html |
From: Aahz <aa...@py...> - 2011-11-26 22:58:39
|
On Sat, Nov 26, 2011, Matthew Brett wrote: > > [2] http://nipyworld.blogspot.com/2011/07/why-you-shouldnt-use-google-code.html Also, Google is killing code search, I wouldn't trust them to keep code, either: http://googleblog.blogspot.com/2011/10/fall-sweep.html -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ "....Normal is what cuts off your sixth finger and your tail..." --Siobhan |
From: Guenter M. <mi...@us...> - 2011-11-28 07:22:36
|
On 2011-11-27, engelbert gruber wrote: > plan > * revoke all write grants to berlios > * svnadmin dump on berlios > * import into sf svn > is it that simple ? Basically. (I hope so.) Some more points: * The daily snapshot build: * do we want to keep it? * can we just move the script (with little adaptions)? * Check documentation for references to berlios.de * update docutils-SVN docs * fix links Could you do this? And in the future: * Check whether we can auto-build the web site (again) with the SVN repo at Docutils. * Consider moving to distributed VS (git, ...) (However, using the repo with `git svn` is already possible and helpfull.) Thanks, Günter |
From: engelbert g. <eng...@gm...> - 2011-12-02 09:38:28
|
did it >> * revoke all write grants to berlios here i failed, i do not have enough rights on berlios (hooks/pre_commit) >> * svnadmin dump on berlios had to be done there, the nightly tree dump is not an svnadmin dump >> * import into sf svn finally worked > * The daily snapshot build: > * do we want to keep it? the key question > * can we just move the script (with little adaptions)? > * Check documentation for references to berlios.de done > * update docutils-SVN docs > * fix links done, but not in sandbox, should i/we > And in the future: > > * Check whether we can auto-build the web site (again) with the SVN repo > at Docutils. > > * Consider moving to distributed VS (git, ...) i think dvcs is a fad mostly :-) > (However, using the repo with `git svn` is already possible and > helpfull.) http://news.gmane.org/group/gmane.text.docutils.cvs did follow subverion checkins how does it switch to https://lists.sourceforge.net/lists/listinfo/docutils-checkins ? we'll see all the best engelbert > Thanks, > > Günter > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Docutils-develop mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-develop > > Please use "Reply All" to reply to the list. -- http://darefoot.blogspot.com |
From: David G. <go...@py...> - 2011-12-06 18:53:45
|
On Fri, Dec 2, 2011 at 04:38, engelbert gruber <eng...@gm...> wrote: > did it Thank you! The rest, we can deal with in good time. It would be nice to get docutils-checkins email notifications from commits working again... I don't remember how to set it up. >> = Guenter Milde: >> * The daily snapshot build: >> * do we want to keep it? > > the key question It would be nice. If we can't, we'll have to remove references to it in the docs & web site. >> And in the future: >> >> * Check whether we can auto-build the web site (again) with the SVN repo >> at Docutils. Would be very useful. The auto-build script is a beast though. It could/should be reimplemented in Python. >> * Consider moving to distributed VS (git, ...) > > i think dvcs is a fad mostly :-) I think DVCSs are here to stay, but we don't need to rush to switch. >> (However, using the repo with `git svn` is already possible and >> helpfull.) > > http://news.gmane.org/group/gmane.text.docutils.cvs did follow > subverion checkins how does it switch to > https://lists.sourceforge.net/lists/listinfo/docutils-checkins ? That's a post-commit hook, I believe. -- David Goodger <http://python.net/~goodger> |
From: engelbert g. <eng...@gm...> - 2011-12-12 11:00:58
|
>>> = Guenter Milde: >>> * The daily snapshot build: >>> * do we want to keep it? >> >> the key question > > It would be nice. If we can't, we'll have to remove references to it > in the docs & web site. AFAIS there is no cron on sf. but one can get a snapshot from viewvc http://docutils.svn.sourceforge.net/viewvc/docutils/?view=tar i have to hone the wording, although it still is a snapshot. cheers > >>> And in the future: >>> >>> * Check whether we can auto-build the web site (again) with the SVN repo >>> at Docutils. > > Would be very useful. The auto-build script is a beast though. It > could/should be reimplemented in Python. > >>> * Consider moving to distributed VS (git, ...) >> >> i think dvcs is a fad mostly :-) > > I think DVCSs are here to stay, but we don't need to rush to switch. > >>> (However, using the repo with `git svn` is already possible and >>> helpfull.) >> >> http://news.gmane.org/group/gmane.text.docutils.cvs did follow >> subverion checkins how does it switch to >> https://lists.sourceforge.net/lists/listinfo/docutils-checkins ? > > That's a post-commit hook, I believe. > > -- > David Goodger <http://python.net/~goodger> -- http://darefoot.blogspot.com |
From: Guenter M. <mi...@us...> - 2011-12-12 12:11:02
|
Dear Engelbert, On 2011-12-12, engelbert gruber wrote: >>>> = Guenter Milde: >>>> * The daily snapshot build: >>>> * do we want to keep it? >> It would be nice. If we can't, we'll have to remove references to it >> in the docs & web site. > AFAIS there is no cron on sf. > but one can get a snapshot from viewvc > http://docutils.svn.sourceforge.net/viewvc/docutils/?view=tar > i have to hone the wording, although it still is a snapshot. Thanks for the work. The equivalent of the "old" daily snapshots (docutils trunk (without branches, tags) and core (without sandbox, prest, and web) is available as gzipped tarball via http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar IMV a link to to this URL can replace the "daily snapshots" creation without loss of functionality. This, some minor edits and a fix to the sandbox snapshot link are in the following patch against my checkout from the SVN. (I removed the DocFactory link, as the DocFactory (like any other sandbox project) can now be easily found and "boxed" via the "browse the sandbox" link.) Günter Exec: svn 'diff' 'index.txt' 2>&1 Dir: /home/milde/Code/Python/docutils-svn/web/ Index: index.txt =================================================================== --- index.txt (Revision 7252) +++ index.txt (Arbeitskopie) @@ -43,6 +43,8 @@ The only **requirement** for running Docutils is Python_ 2.3 or later. (For Docutils 0.5, Python 2.2.1+ is required. Up to Docutils 0.4, Python 2.1 is required.) +From version 0.6, Docutils is compatible with Python 3 (see README_ for +details). Docutils is in active development and should be considered **experimental**. APIs are subject to change at any time. @@ -51,13 +53,10 @@ Download ======== -We recommend that you use the latest **snapshot**, -`<docutils-snapshot.tgz>`_. The snapshots usually contain *more -features* and *fewer bugs* than the "official" releases |---| they're -not only for developers! +We recommend that you use a snapshot_ from `Docutils' Subversion +repository`_. The snapshots usually contain *more features* and *fewer bugs* +than the "official" releases |---| they're not only for developers! -From version 0.6 Docutils is compatible with Python 3, but requires 2to3. - The latest **release package** is `docutils-0.8.1.tgz`__. It was released on 2011-07-08 and is mostly intended for distributors. See the `release notes`_ for a list of changes since the previous release @@ -66,19 +65,14 @@ __ http://prdownloads.sourceforge.net/docutils/docutils-0.8.1.tar.gz?download .. _release notes: RELEASE-NOTES.html#release-0-8-1-2011-08-30 -More snapshots: +The Sandbox_ contains experimental, contributed code. You can download a +complete `snapshot of the Sandbox`_ or `browse the Sandbox`_ to download a +subset. -- `Snapshot of the Sandbox`_ (experimental, contributed code; see the - Sandbox_ for details) -- `Snapshot of DocFactory project files`_ (this is a subset of the - Sandbox snapshot above; you don't need both) - -You can also access `Docutils' Subversion repository`_ directly. - .. attention:: The repository was moved on 2011-12-02 at revision 7232 - from |BerliOS|_ to |SourceForge|_. + from BerliOS to |SourceForge|_. - Subversion repository *was* hosted by |BerliOS|_ for years, + Subversion repository was hosted by |BerliOS|_ for years, *many thanks for the support*. .. class:: credits @@ -104,11 +98,12 @@ .. _dugui: http://docutils.sourceforge.net/sandbox/dugui/ .. _LaTeX math support: http://docutils.sourceforge.net/sandbox/latex_directive/ -.. _latest snapshot: http://docutils.sourceforge.net/docutils-snapshot.tgz +.. _snapshot: + http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar .. _Snapshot of the Sandbox: - http://docutils.sourceforge.net/docutils-sandbox-snapshot.tgz -.. _Snapshot of DocFactory project files: - http://docutils.sourceforge.net/docfactory-snapshot.tgz + http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/sandbox/?view=tar +.. _browse the Sandbox: + http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/sandbox/ .. _bug report: http://sourceforge.net/tracker/?group_id=38414&atid=422030 .. _patch tracker: http://sourceforge.net/tracker/?group_id=38414&atid=422032 .. _mailing lists: docs/user/mailing-lists.html |
From: engelbert g. <eng...@gm...> - 2011-12-12 21:31:15
|
committed and updated the web site cheers On Mon, Dec 12, 2011 at 1:10 PM, Guenter Milde <mi...@us...> wrote: > Dear Engelbert, > > On 2011-12-12, engelbert gruber wrote: >>>>> = Guenter Milde: > >>>>> * The daily snapshot build: >>>>> * do we want to keep it? > >>> It would be nice. If we can't, we'll have to remove references to it >>> in the docs & web site. > >> AFAIS there is no cron on sf. >> but one can get a snapshot from viewvc >> http://docutils.svn.sourceforge.net/viewvc/docutils/?view=tar > >> i have to hone the wording, although it still is a snapshot. > > Thanks for the work. > > The equivalent of the "old" daily snapshots (docutils trunk (without > branches, tags) and core (without sandbox, prest, and web) is available > as gzipped tarball via > > http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar > > IMV a link to to this URL can replace the "daily snapshots" creation without > loss of functionality. > > This, some minor edits and a fix to the sandbox snapshot link are in the > following patch against my checkout from the SVN. > > (I removed the DocFactory link, as the DocFactory (like any other sandbox > project) can now be easily found and "boxed" via the "browse the sandbox" > link.) > > Günter > > Exec: svn 'diff' 'index.txt' 2>&1 > Dir: /home/milde/Code/Python/docutils-svn/web/ > > Index: index.txt > =================================================================== > --- index.txt (Revision 7252) > +++ index.txt (Arbeitskopie) > @@ -43,6 +43,8 @@ > The only **requirement** for running Docutils is Python_ 2.3 or later. > (For Docutils 0.5, Python 2.2.1+ is required. > Up to Docutils 0.4, Python 2.1 is required.) > +From version 0.6, Docutils is compatible with Python 3 (see README_ for > +details). > > Docutils is in active development and should be considered **experimental**. > APIs are subject to change at any time. > @@ -51,13 +53,10 @@ > Download > ======== > > -We recommend that you use the latest **snapshot**, > -`<docutils-snapshot.tgz>`_. The snapshots usually contain *more > -features* and *fewer bugs* than the "official" releases |---| they're > -not only for developers! > +We recommend that you use a snapshot_ from `Docutils' Subversion > +repository`_. The snapshots usually contain *more features* and *fewer bugs* > +than the "official" releases |---| they're not only for developers! > > -From version 0.6 Docutils is compatible with Python 3, but requires 2to3. > - > The latest **release package** is `docutils-0.8.1.tgz`__. It was > released on 2011-07-08 and is mostly intended for distributors. See > the `release notes`_ for a list of changes since the previous release > @@ -66,19 +65,14 @@ > __ http://prdownloads.sourceforge.net/docutils/docutils-0.8.1.tar.gz?download > .. _release notes: RELEASE-NOTES.html#release-0-8-1-2011-08-30 > > -More snapshots: > +The Sandbox_ contains experimental, contributed code. You can download a > +complete `snapshot of the Sandbox`_ or `browse the Sandbox`_ to download a > +subset. > > -- `Snapshot of the Sandbox`_ (experimental, contributed code; see the > - Sandbox_ for details) > -- `Snapshot of DocFactory project files`_ (this is a subset of the > - Sandbox snapshot above; you don't need both) > - > -You can also access `Docutils' Subversion repository`_ directly. > - > .. attention:: The repository was moved on 2011-12-02 at revision 7232 > - from |BerliOS|_ to |SourceForge|_. > + from BerliOS to |SourceForge|_. > > - Subversion repository *was* hosted by |BerliOS|_ for years, > + Subversion repository was hosted by |BerliOS|_ for years, > *many thanks for the support*. > > .. class:: credits > @@ -104,11 +98,12 @@ > .. _dugui: http://docutils.sourceforge.net/sandbox/dugui/ > .. _LaTeX math support: > http://docutils.sourceforge.net/sandbox/latex_directive/ > -.. _latest snapshot: http://docutils.sourceforge.net/docutils-snapshot.tgz > +.. _snapshot: > + http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar > .. _Snapshot of the Sandbox: > - http://docutils.sourceforge.net/docutils-sandbox-snapshot.tgz > -.. _Snapshot of DocFactory project files: > - http://docutils.sourceforge.net/docfactory-snapshot.tgz > + http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/sandbox/?view=tar > +.. _browse the Sandbox: > + http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/sandbox/ > .. _bug report: http://sourceforge.net/tracker/?group_id=38414&atid=422030 > .. _patch tracker: http://sourceforge.net/tracker/?group_id=38414&atid=422032 > .. _mailing lists: docs/user/mailing-lists.html > > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Docutils-develop mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-develop > > Please use "Reply All" to reply to the list. -- http://darefoot.blogspot.com |
From: engelbert g. <eng...@gm...> - 2011-12-17 13:58:10
|
next step On Tue, Dec 6, 2011 at 7:53 PM, David Goodger <go...@py...> wrote: >>> And in the future: >>> >>> * Check whether we can auto-build the web site (again) with the SVN repo >>> at Docutils. > > Would be very useful. The auto-build script is a beast though. > It could/should be reimplemented in Python. what should this script do * publish trunk/web and trunk/docutils/docs currently it puts trunk/docutils on the web, all python code all the sandbox test (http://http://docutils.sourceforge.net/test/) but this is all accessable via the subversion repository viewvc. the beast could be cut down a lot cheers engelbert -- http://darefoot.blogspot.com |
From: David G. <go...@py...> - 2011-12-17 14:58:01
|
On Sat, Dec 17, 2011 at 08:58, engelbert gruber <eng...@gm...> wrote: > next step > > On Tue, Dec 6, 2011 at 7:53 PM, David Goodger <go...@py...> wrote: >>>> And in the future: >>>> >>>> * Check whether we can auto-build the web site (again) with the SVN repo >>>> at Docutils. >> >> Would be very useful. The auto-build script is a beast though. >> It could/should be reimplemented in Python. > > what should this script do > > * publish trunk/web and trunk/docutils/docs And all the .txt files in trunk/docutils also (README.txt, etc.) > currently it puts trunk/docutils on the web, all python code all the sandbox > test (http://http://docutils.sourceforge.net/test/) but this is all > accessable via > the subversion repository viewvc. The sandbox also contains many .txt files that need to be converted to .html. I like the non-viewvc publishing of code. It's an easy way to refer to modules (clean, easy URLs), and I'd rather have it stay. > the beast could be cut down a lot Perhaps, but my point was that a Python version would be much easier to maintain. Let's keep the two topics (rewrite in Python vs. re-engineer the functionality) separate. As engineers, we have a bad tendency to conflate the two :-) -- David Goodger <http://python.net/~goodger> |