From: Frank W. <fwi...@gm...> - 2009-03-29 22:23:10
|
We are getting very close to shipping a release candidate, and from there it shouldn't be too far from GA. At that point I'd like to figure out an exit strategy from Sourceforge, or, given some recent improvements at Sourceforge, shift the way we use Sourceforge. My first impulse is to move to the Python.org infrastructure. Jim Baker and I are now members of the PSF, and Jim, Philip Jenvey, and I have a commit bit to CPython for fixing Lib and Lib/test for Jython compatibility. Barry Warsaw has already offered to help get our mail over, and I believe we could convince them to take our web presence and let us become a parallel project in their repo, but I don't want to ask unless this is what we all decide to do. From what I have heard, they will decide on a DVCS before the Pycon sprints are over (this Thursday). They are down to hg and bzr, either of which would work for me. My second thought would be to move to Kenai, because JRuby and all of the projects we share with JRuby (jna-posix and constantine) are there. We would probably use hg there unless there is a strong desire to use git. I don't think we could move our mail archives there, but we could freeze our old mailer and start a new mailing list at Kenai. Since Sourceforge recently started supporting an assortment of DVCS, bug trackers, etc, we could also take a new look at our Sourceforge options (I'm not crazy about this one, honestly). Where do you guys want to go? -Frank |
From: Steven G. <swg...@mt...> - 2009-03-29 23:53:29
|
I think it would be kind of cool to be a first class python.org project. -steve Frank Wierzbicki wrote: > We are getting very close to shipping a release candidate, and from > there it shouldn't be too far from GA. At that point I'd like to > figure out an exit strategy from Sourceforge, or, given some recent > improvements at Sourceforge, shift the way we use Sourceforge. > > My first impulse is to move to the Python.org infrastructure. Jim > Baker and I are now members of the PSF, and Jim, Philip Jenvey, and I > have a commit bit to CPython for fixing Lib and Lib/test for Jython > compatibility. Barry Warsaw has already offered to help get our mail > over, and I believe we could convince them to take our web presence > and let us become a parallel project in their repo, but I don't want > to ask unless this is what we all decide to do. From what I have > heard, they will decide on a DVCS before the Pycon sprints are over > (this Thursday). They are down to hg and bzr, either of which would > work for me. > > My second thought would be to move to Kenai, because JRuby and all of > the projects we share with JRuby (jna-posix and constantine) are > there. We would probably use hg there unless there is a strong desire > to use git. I don't think we could move our mail archives there, but > we could freeze our old mailer and start a new mailing list at Kenai. > > Since Sourceforge recently started supporting an assortment of DVCS, > bug trackers, etc, we could also take a new look at our Sourceforge > options (I'm not crazy about this one, honestly). > > Where do you guys want to go? > > -Frank > > ------------------------------------------------------------------------------ > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Jim B. <jb...@zy...> - 2009-03-30 15:25:22
|
Like Steve, I believe being on python.org would help facilitate our push to make Jython a first-class Python community project. We can continue sharing with JRuby, not to mention other JVM language implementations, on jna-posix, constantine, and new projects like the regex engine, JSR-223 replacement/MOP, etc. But these components are -- and need to be -- more black box anyway for the sharing to work in practice. Kenai will continue to be a good place to host these and other related projects, much like we are using github (clamp) and googlecode (Django on Jython) as well. - Jim On Sun, Mar 29, 2009 at 5:53 PM, Steven Githens <swg...@mt...> wrote: > I think it would be kind of cool to be a first class python.org project. > > -steve > > Frank Wierzbicki wrote: > > We are getting very close to shipping a release candidate, and from > > there it shouldn't be too far from GA. At that point I'd like to > > figure out an exit strategy from Sourceforge, or, given some recent > > improvements at Sourceforge, shift the way we use Sourceforge. > > > > My first impulse is to move to the Python.org infrastructure. Jim > > Baker and I are now members of the PSF, and Jim, Philip Jenvey, and I > > have a commit bit to CPython for fixing Lib and Lib/test for Jython > > compatibility. Barry Warsaw has already offered to help get our mail > > over, and I believe we could convince them to take our web presence > > and let us become a parallel project in their repo, but I don't want > > to ask unless this is what we all decide to do. From what I have > > heard, they will decide on a DVCS before the Pycon sprints are over > > (this Thursday). They are down to hg and bzr, either of which would > > work for me. > > > > My second thought would be to move to Kenai, because JRuby and all of > > the projects we share with JRuby (jna-posix and constantine) are > > there. We would probably use hg there unless there is a strong desire > > to use git. I don't think we could move our mail archives there, but > > we could freeze our old mailer and start a new mailing list at Kenai. > > > > Since Sourceforge recently started supporting an assortment of DVCS, > > bug trackers, etc, we could also take a new look at our Sourceforge > > options (I'm not crazy about this one, honestly). > > > > Where do you guys want to go? > > > > -Frank > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Jython-dev mailing list > > Jyt...@li... > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > -- Jim Baker jb...@zy... |
From: Oti <oh...@gm...> - 2009-03-30 21:54:18
|
Nothing speaks against python.org in the long run. No hurry from my side, though. What I really need is a rock solid eclipse team plugin if we should change version control ;-) best wishes, Oti. 2009/3/30 Jim Baker <jb...@zy...>: > Like Steve, I believe being on python.org would help facilitate our push to > make Jython a first-class Python community project. > We can continue sharing with JRuby, not to mention other JVM language > implementations, on jna-posix, constantine, and new projects like the regex > engine, JSR-223 replacement/MOP, etc. But these components are -- and need > to be -- more black box anyway for the sharing to work in practice. Kenai > will continue to be a good place to host these and other related projects, > much like we are using github (clamp) and googlecode (Django on Jython) as > well. > - Jim > On Sun, Mar 29, 2009 at 5:53 PM, Steven Githens <swg...@mt...> wrote: >> >> I think it would be kind of cool to be a first class python.org project. >> >> -steve >> >> Frank Wierzbicki wrote: >> > We are getting very close to shipping a release candidate, and from >> > there it shouldn't be too far from GA. At that point I'd like to >> > figure out an exit strategy from Sourceforge, or, given some recent >> > improvements at Sourceforge, shift the way we use Sourceforge. >> > >> > My first impulse is to move to the Python.org infrastructure. Jim >> > Baker and I are now members of the PSF, and Jim, Philip Jenvey, and I >> > have a commit bit to CPython for fixing Lib and Lib/test for Jython >> > compatibility. Barry Warsaw has already offered to help get our mail >> > over, and I believe we could convince them to take our web presence >> > and let us become a parallel project in their repo, but I don't want >> > to ask unless this is what we all decide to do. From what I have >> > heard, they will decide on a DVCS before the Pycon sprints are over >> > (this Thursday). They are down to hg and bzr, either of which would >> > work for me. >> > >> > My second thought would be to move to Kenai, because JRuby and all of >> > the projects we share with JRuby (jna-posix and constantine) are >> > there. We would probably use hg there unless there is a strong desire >> > to use git. I don't think we could move our mail archives there, but >> > we could freeze our old mailer and start a new mailing list at Kenai. >> > >> > Since Sourceforge recently started supporting an assortment of DVCS, >> > bug trackers, etc, we could also take a new look at our Sourceforge >> > options (I'm not crazy about this one, honestly). >> > >> > Where do you guys want to go? >> > >> > -Frank >> > >> > >> > ------------------------------------------------------------------------------ >> > _______________________________________________ >> > Jython-dev mailing list >> > Jyt...@li... >> > https://lists.sourceforge.net/lists/listinfo/jython-dev >> > >> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > -- > Jim Baker > jb...@zy... > > ------------------------------------------------------------------------------ > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > > |
From: Frank W. <fwi...@gm...> - 2009-03-30 22:08:25
|
On Mon, Mar 30, 2009 at 5:54 PM, Oti <oh...@gm...> wrote: > Nothing speaks against python.org in the long run. > No hurry from my side, though. > What I really need is a rock solid eclipse team plugin if we should > change version control ;-) There is this http://www.vectrace.com/mercurialeclipse/ and if you haven't heard Python has gone with mercurial. -Frank |
From: Alan K. <jyt...@xh...> - 2009-03-31 15:50:55
|
[Jim] > Like Steve, I believe being on python.org would help facilitate our push to > make Jython a first-class Python community project. I completely agree: we should be aiming to get jython onto python.org infrastructure. Sharing infrastructure, tools, etc, with them will facilitate closer ties between the communities, which will benefit us all. Regards, Alan. |
From: Josh J. <jun...@gm...> - 2009-04-01 05:57:14
|
+1 from a non-Jython developer (only bug fixes and django-jython) I think being on python.org is the way to go. Ultimately, we would like to see Jython as the JVM adaptation of Python, so I think it makes sense to have both projects reside in the same domain. Josh Juneau jun...@gm... http://jj-blogger.blogspot.com http://www.gathereventplanning.com Twitter ID: javajuneau On Tue, Mar 31, 2009 at 8:50 AM, Alan Kennedy <jyt...@xh...> wrote: > [Jim] > > Like Steve, I believe being on python.org would help facilitate our push > to > > make Jython a first-class Python community project. > > I completely agree: we should be aiming to get jython onto python.org > infrastructure. Sharing infrastructure, tools, etc, with them will > facilitate closer ties between the communities, which will benefit us > all. > > Regards, > > Alan. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |