David Bremner <david@tethera.net> writes: > Wael Nasreddine <wael.nasreddine@gmail.com> writes: > >> I didn't see the previous email about it, thank you Jani for the link. It >> looks like you guys have your hands full and everything setup the way you >> like it, so here's what I'll do myself (if it's acceptable with you, >> otherwise I'll just remove everything): >> >> - Revert my changes (except for the CI) >> - Set a cron job to update the mirror hourly for the Github user wanting to >> fork. >> - Remove the Issues, Pull Request and the Wiki >> - Add a "mirror of .." to the description on top of the page >> - Manually update the contrib/ bindings/ as they change in here and maybe >> automate it later. >> >> For the automatic pusher, I'll have to skip the README changes. > > I think the concensus among the devs is that if there is going to be a > "notmuch" organization on github then it should be owned by and > controlled by us. > Let me expand on that comment a bit. It's great that you want to run a CI instance (we already have one, but who knows, maybe this will catch some problems our current instance does not). It's also fine that you want to run a mirror, or even (obviously) distribute modified versions of notmuch. The main point that many of us are sensitive about is people confusing these modified versions (and yeah, I consider splitting the repo modification) with the official one. The other point is that by admining the "notmuch" project on github, you are somehow officially representing the project to the outside world. Maybe if we get to know you, and we develop the appropriate communications channels, we'd think that would be a great idea, but it seems like too much to entrust to somebody we just "met". d