I can help with any of these items. I can probably spend one full day on it on Friday.
-ww On Jun 13, 2012, at 12:27 AM, anatoly techtonik wrote: > On Wed, Jun 13, 2012 at 4:19 AM, Richard Jones <[email protected]> wrote: >> On 13 June 2012 09:14, Steve <[email protected]> wrote: >>> Also, it's kind of hard (or unclear how) to fork the project and submit >>> patches. While the web site is being updated, updates to the Contribute page >>> would be nice. (Or a move off of Google Code for the canonical repo.) >> >> At the moment there is no formal process. You create an issue and >> provide the patch / fork details there. >> >> Google Code doesn't support automated pull requests like >> bitbucket/github. I think that's a big failing and a reasonable >> motivation to move to bitbucket, but that's probably just a >> distraction from doing more productive things. It might also make the >> website maintenance simpler too - at the moment I'm the only (active) >> person with access to update the website. If it was hosted via >> bitbucket with post-commit hooks then things would be simpler. Also, >> we need to fix or replace epydoc as I cannot make it work - which is >> why the website hasn't been updated in quite some time. I am still >> trying but I suspect I'll be tossing it out and using Sphinx soon. >> >> I believe the biggest hurdle in getting a 1.2 release out is that the >> cocoa port needs to be merged into the default branch. Once that's >> done I'd be happy to push out a source 1.2 release. > > So, what are the action items [ ] and stumbling blocks (s)? > > ---Pri-1--- > [ ] update web site > [ ] fix epydoc > [ ] add an issue to tracker > [ ] move web site to Bitbucket > [ ] create group 'pyglet' > [ ] add repository pyglet.bitbucket.org > (see > https://confluence.atlassian.com/display/BITBUCKET/Publishing+a+Website+on+bitbucket) > [ ] add CNAME for pyglet.org to pyglet.bitbucket.org > (I am not sure, but it should work) > [ ] mention 1.2 > [ ] direct link to Google Code from top menu > [ ] update Contribute to be clear > [ ] send patches > [ ] site in repository is broken > http://code.google.com/p/pyglet/source/browse/#hg%2Fwebsite > [ ] write instructions / fix it to work from checkout > (s) Richard needs time > > [ ] merge cocoa port > > [ ] write README > (s) how is pyglet 1.2 different from 1.1? > [ ] support 64bit Python > [ ] write ANNOUNCEMENT > (s) what's new? > > ---Pri-2--- > [ ] update wiki pages > [ ] draw a line on http://code.google.com/p/pyglet/wiki/ReleaseSchedule > [ ] integrate patches > (s) Richard > > [ ] update issue tracker > [ ] add website label to issue tracker > [ ] allow users to assign labels when creating new issues > [ ] add 1.2 milestone > (s) Richard > > ---Pri-3--- > [ ] build a windows installer > [ ] try > [ ] list problems > > > So, who can help with any of the stuff above? > Is there anything is missing? > Is there anybody besides Richard with an access to wiki? > Or we can use http://wiki.python.org/moin/Pyglet, because: > 1. it is free-for-all > 2. you can subscribe to pages to be notified about changes > > Yes/No? > -- > anatoly t. > > -- > You received this message because you are subscribed to the Google Groups > "pyglet-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/pyglet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
