On Sep 1, 2013, at 9:11 AM, Johan Brichau <[email protected]> wrote:
> > On 31 Aug 2013, at 17:45, Tobias Pape <[email protected]> wrote: > >>> That is like saying everyone have to be in the Seaside team to upload just >>> a fix in Grease? >> >> >> Then make a grease team. >> Grease was invented for Seaside by the seaside team, doesn't >> that make the Seaside team the official maintainer? >> Then yes, everyone who wants his fix in the official Grease >> repo has to be on that team or ask someone there to merge/integrate/upload. > > > Does it really matter if you need to be on the Seaside team for contributing > to only a specific sub project? not really. you could be a contributor of a project (not a team), and not part of the team... you could be part of Grease project without having anything to do with the rest of Seaside. > For example, Damien recently contributed fixes to the configurations and > therefore I added him to the Seaside team. > > Easy. done. > > Apart from that, it makes sense to move Grease to its own project. > I'm not an author of Grease, but I did the move of Seaside to Smalltalkhub > and raised the issue about Grease not having its proper project on the > Seaside-dev mailinglist while doing this back in July. > If I remember correctly, there was no opposition to moving it to its separate > space if this helped development. The reason it did not happen yet is that I > previously thought we needed to merge the two Grease versions from the two > Seaside repositories to a single one. But now I realise that we should only > move the most recent one (the one from Seaside31). > > ESUG is coming up. If we did not do it by then, talk to us. > > Cheers > Johan
