On Tue, Apr 27, 2010 at 2:44 AM, Florian Bösch <[email protected]> wrote: > On Apr 27, 4:51 am, Joe Wreschnig <[email protected]> wrote: >> On Sat, Apr 17, 2010 at 12:19 AM, Joe Wreschnig <[email protected]> >> wrote: >> I've done several commits to my clone now, but no one's answered my >> real question. Barring anything else, this is a request for mainline >> push privileges. > > There's four primary ways changes from your repository make your way > into pyglets main repository: > > - get somebody who has push rights on pyglets main repository to pull > your changes and to push them to pyglets main repository (I prefer > this, because there's a slight chance that somebody would also look at > the changes) > - export a changeset bundle from your repository and give it to > somebody who has pyglet main repository push rights > - provide a patch queue with changes so somebody else can clone and > qpush your patches, and if satisfied merge them in and push them to > the main pyglet repository (the advantage of this is, that you can do > continous integration, and the patch won't make it into the history > until everybody's satisfied)
These all work great in theory - in fact my original question was basically "hey, which of these should I do?" But it only works if the project has dedicated owners and reviewers. When there's only 2-3 semi-active developers, these workflows become a crapshoot of pestering emails (which is what I'm doing). That's time-consuming for everyone involved. Did you look at my repository to see if the thing in it should be merged? I doubt it, since you didn't comment on it at all. So even your preferred method is not getting my changes reviewed or merged. > - get push rights yourself (I actually prefer this the least, because > it doesn't "force" any kind of social organization on our part) So I'm left with this as the only option, aside from a long-term fork, to get changes out in a reliable and timely manner. -- 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.
