Let's go! :) Thanks for taking the initiative Henry.
2016-05-17 12:36 GMT-07:00 Henry Saputra <[email protected]>: > We could also add user@ list if needed. > > If no objection, I will submit creation for both issues@ and users@ lists > for metamodel. > > - Henry > > On Mon, May 16, 2016 at 11:46 AM, Kasper Sørensen < > [email protected]> wrote: > >> I think that sounds like a good idea. >> >> I've also been pondering on whether we should have a users@ list for >> people who have end-user questions. Right now the dev list is a mix of >> MetaModel core developers and developers who are users of MetaModel. >> OTOH it's not like we're drowning in (non-spam) mails, so I am just >> wondering what is most comfortable for everyone, and if adding a users >> list will maybe even invite more people to use it. >> >> 2016-05-16 11:41 GMT-07:00 Henry Saputra <[email protected]>: >> > In lieu the spammer case for our JIRA, I am proposing to create new list >> > called issues@ to where ALL JIRA update emails will be sent. >> > >> > Hopefully this will make dev@ list to be safe haven to have tech >> > discussions. >> > >> > Thoughts? >> > >> > - Henry >> > >> > On Fri, May 13, 2016 at 1:35 PM, Kasper Sørensen < >> > [email protected]> wrote: >> > >> >> And it seems there's a bit more spam coming through the filters now. >> >> I'm on the infra chat to try and do something about it. >> >> >> >> 2016-05-12 10:11 GMT-07:00 Kasper Sørensen < >> [email protected] >> >> >: >> >> > Hi all, >> >> > >> >> > First of all: I hope you are still with us on the mailing list. If you >> >> > are, you have no doubt noticed a lot of unwanted spam activity on JIRA >> >> > and thus also on the mailing list today. >> >> > >> >> > It happened even though the ASF JIRA was _already_ in a lockdown mode >> >> > due to spam on all the projects. The lockdown mode means that only >> >> > committers and admins etc. are allowed to create issues. Somehow the >> >> > spammers managed to circumvent this permission scheme for the >> >> > METAMODEL project. Infra is looking into how that could be... >> >> > >> >> > A short term solution is now in place though: Our JIRA is for the >> >> > moment in complete read-only mode. >> >> > >> >> > What does this mean for us? Here's my suggestion: >> >> > * We cannot clean up your inbox for you. So delete the mails you got >> >> > today (except maybe this one :)) >> >> > * Infra will delete the issues on JIRA for us. >> >> > * If you want to report a new issue or discuss/change an existing >> >> > issue - for the moment simply do this via email to this mailing list >> >> > ([email protected]) >> >> > * If you have a patch that you want to share, GitHub and the >> >> > reviewboard are both still operational. >> >> > * When we accept patches then make sure to update CHANGES.md. Since >> >> > JIRA is not useful right now, we will use CHANGES.md as our way of >> >> > tracking what has been done and then update JIRA when possible. >> >> > >> >> > Should something like this ever happen again, then the ASF infra guys >> >> > on HipChat are nice and responsive. Just go to this URL and let them >> >> > know: >> >> > https://www.hipchat.com/gIjVtYcNy >> >> > >> >> > Thank you all for your patience. >> >> > >> >> > Best regards, >> >> > Kasper >> >> >>
