live.gnome.org Maintenance
Hi, tomorrow morning (from 10 AM, GMT +2) there will be a downtime of live.gnome.org, we're switching the wiki over a new machine since we're experiencing high loads and problems while loading pages. I'll follow up this mail with more details as soon as the migration will be completely done. If you have any question, please join #sysadmin on GIMPNET. cheers, Andrea signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: live.gnome.org Maintenance
On Fri, 18 May 2012, Andrea Veri wrote: > Hi, > > tomorrow morning (from 10 AM, GMT +2) there will be a downtime of > live.gnome.org, we're switching the wiki over a new machine since > we're experiencing high loads and problems while loading pages. > > I'll follow up this mail with more details as soon as the migration > will be completely done. > > If you have any question, please join #sysadmin on GIMPNET. live.gnome.org will go under MAINTENANCE in a few minutes while I migrate the content to the new host I finished setting up yesterday night. Another mail will follow as soon as everything got migrated. cheers, Andrea signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: live.gnome.org Maintenance
On Tue, 22 May 2012, Andrea Veri wrote: > [...] > live.gnome.org will go under MAINTENANCE in a few minutes while I > migrate the content to the new host I finished setting up yesterday > night. > > Another mail will follow as soon as everything got migrated. The migration has just finished and the following wikis now have a new home: 1. live.gnome.org 2. pango.org 3. gnome-db.org (still needs DNS to be updated since we don't manage it) Have a nice day everyone and thanks for your patience, Andrea signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: live.gnome.org Maintenance
On Tue, 22 May 2012, Andrea Veri wrote: > On Tue, 22 May 2012, Andrea Veri wrote: > > > [...] > > live.gnome.org will go under MAINTENANCE in a few minutes while I > > migrate the content to the new host I finished setting up yesterday > > night. > > > > Another mail will follow as soon as everything got migrated. > > The migration has just finished and the following wikis now have a new > home: > > 1. live.gnome.org > 2. pango.org > 3. gnome-db.org (still needs DNS to be updated since we don't manage it) Everything should be back to normality now, I've managed to renew a good bunch of SSL certs as well and enabled 443 on several virtual hosts. Please report any error or malfunctioning you may find either by opening a bug on the 'sysadmin' product in bugzilla or join #sysadmin on GIMPNET. Enjoy! Andrea signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME Bugmail: Gmail threading finally working!
Hi, I introduced a little fix yesterday night that will modify how bugmail's subjects appear, that for Gmail's threading to work properly. (as you may know Gmail doesn't look for the In-Reply-To: header but for the subject instead) New bugs won't be marked with the 'New:' tag anymore while replies will append a 'Re:' as it usually happens with the majority of mail clients. I would like to thank Jasper St. Pierre for pushing this forward! Have a nice day everyone, -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME Bugmail: Gmail threading finally working!
I'm really wondering what's the rationale behind forwarding a fix that has been applied upstream in newer Bugzilla releases already. Newer Bugzillas do have a specific flag to manage Gmail's threading directly on the email preferences for each single user. This was just a temporary measure until we upgrade our Bugzilla to the 4.2 release. Up to you, really. 2012/12/12 Olav Vitters > On Wed, Dec 12, 2012 at 02:15:30PM +0100, Andrea Veri wrote: > > I introduced a little fix yesterday night that will modify how bugmail's > > subjects appear, that for Gmail's threading to work properly. (as you may > > know Gmail doesn't look for the In-Reply-To: header but for the subject > > instead) > > > > New bugs won't be marked with the 'New:' tag anymore while replies will > > append a 'Re:' as it usually happens with the majority of mail clients. > > > > I would like to thank Jasper St. Pierre for pushing this forward! > > I undid that change as you didn't say to me you were making changes. > Furthermore it it broke my filtering, it won't work in every case, it > should be pushed upstream first, secondly you made the change on the > server, not in the repository. > > Regarding does not work, "Re:" is not needed for threading. In-Reply-To > and so on are. Gmail only threads by subject, so any time the subject is > adjusted it'll break again. > > Please make the change *upstream* first, I cannot maintain Bugzilla as > it is now. > > I do really appreciate all the work you're doing. Please do not see > above as a "stop", but prefer if someone would takeover the maintenance, > not small changes which increase maintenance. > > -- > Regards, > Olav > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Bugzilla upgrade? [was: Re: GNOME Bugmail: Gmail threading finally working!]
Thanks for bringing this up Andre. I can try to work on the upgrade but I never touched Bugzilla before since Olav was used to manage it. I've searched around for the upgrade documentation [1] and it doesn't look like an hard operation. We should probably wait for Olav to provide some more details about the modifications that GNOME made to customize our installation, that might be the only bottleneck for a possible upgrade. But let's keep all the ports open, having someone to assist me during the operations will definitely speed everything up for this matter. 2012/12/12 Andre Klapper > On Wed, 2012-12-12 at 16:06 +0100, Andrea Veri wrote: > > This was just a temporary measure until we upgrade our Bugzilla to the > 4.2 > > release. > > Which brings us to the bigger question how to get GNOME Bugzilla from > 3.4 to 4.2. I don't even know if somebody cares to check and backports > security upgrades to GNOME Bugzilla. > IIRC, when upgrading from 2.20 to 3.4 we received gracious sponsoring by > Canonical to pay Max for this task. > If nobody has plans to try, this might be something to defer to the > foundation board in order to organize sponsoring? > > I guess I don't need to copy and paste all improvements from the last > three upstream release notes to explain why I push for upgrading. > > andre > -- > Andre Klapper | ak...@gmx.net > http://blogs.gnome.org/aklapper/ > > ___ > foundation-list mailing list > foundation-l...@gnome.org > https://mail.gnome.org/mailman/listinfo/foundation-list > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Bugzilla upgrade? [was: Re: GNOME Bugmail: Gmail threading finally working!]
And the link: [1] http://www.bugzilla.org/docs/4.2/en/html/upgrade.html 2012/12/12 Andrea Veri > Thanks for bringing this up Andre. I can try to work on the upgrade but I > never touched Bugzilla before since Olav was used to manage it. I've > searched around for the upgrade documentation [1] and it doesn't look like > an hard operation. We should probably wait for Olav to provide some more > details about the modifications that GNOME made to customize our > installation, that might be the only bottleneck for a possible upgrade. > > But let's keep all the ports open, having someone to assist me during the > operations will definitely speed everything up for this matter. > > > 2012/12/12 Andre Klapper > >> On Wed, 2012-12-12 at 16:06 +0100, Andrea Veri wrote: >> > This was just a temporary measure until we upgrade our Bugzilla to the >> 4.2 >> > release. >> >> Which brings us to the bigger question how to get GNOME Bugzilla from >> 3.4 to 4.2. I don't even know if somebody cares to check and backports >> security upgrades to GNOME Bugzilla. >> IIRC, when upgrading from 2.20 to 3.4 we received gracious sponsoring by >> Canonical to pay Max for this task. >> If nobody has plans to try, this might be something to defer to the >> foundation board in order to organize sponsoring? >> >> I guess I don't need to copy and paste all improvements from the last >> three upstream release notes to explain why I push for upgrading. >> >> andre >> -- >> Andre Klapper | ak...@gmx.net >> http://blogs.gnome.org/aklapper/ >> >> ___ >> foundation-list mailing list >> foundation-l...@gnome.org >> https://mail.gnome.org/mailman/listinfo/foundation-list >> > > > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GIT MAINTENANCE: 23th Apr, 11:00 - 12:30 GMT+2
Hi, I'm currently migrating git.gnome.org to a new machine, there will be a little downtime tomorrow 23th April from 11:00 - 12:30 GMT+2. The service involved will be shutdown to prevent any data loss during the move. As always I'll make sure to follow-up this e-mail to confirm that the move went smoothly. Have an awesome day, -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GIT MAINTENANCE: 23th Apr, 11:00 - 12:30 GMT+2
Everything should be back. Please let me know if you experience any issue. Thanks! Andrea 2013/4/22 Andrea Veri > Hi, > > I'm currently migrating git.gnome.org to a new machine, there will be a > little downtime tomorrow 23th April from 11:00 - 12:30 GMT+2. > > The service involved will be shutdown to prevent any data loss during the > move. As always I'll make sure to follow-up this e-mail to confirm that the > move went smoothly. > > Have an awesome day, > > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Services is now MeetBot capable
Hello guys, from today the Services bot will be able to manage / log meetings by using the MeetBot plugin. The logs will be publicly available at [1]. For more information about the plugin itself and how to run your own meetings, please check [2]. A preview of how things will look like is available at the Fedora Project's meetbot page at [3]. Please don't abuse the new functionality with random tests. Hope you will enjoy this new feature and make good use of it. Have an awesome day! [1] http://meetbot.gnome.org [2] http://meetbot.gnome.org/Manual.html [3] http://meetbot.fedoraproject.org/ -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: New GnomeGoal proposal: InstalledTests
2013/4/26 Tristan Van Berkom > On Sat, Apr 27, 2013 at 1:56 AM, Colin Walters wrote: > >> On Fri, 2013-04-26 at 18:49 +0200, Emilio Pozuelo Monfort wrote: >> > Hi, >> > >> > On 04/26/2013 05:01 PM, Colin Walters wrote: >> > > On Fri, 2013-04-26 at 10:32 -0400, Dan Winship wrote: >> > >> I want "make distcheck" to still run all of my tests, to guarantee >> that >> > >> everything works correctly when built from a tarball, not just when >> > >> built from git. >> > > >> > > That's going to be a high bar to jump; but I suppose it makes sense to >> > > have both during the transition and give downstreams time to teach >> their >> > > build systems about revision control. >> > >> > I'm not sure I follow here. Are you implying that you want to stop >> making >> > tarballs eventually? >> >> Yes. >> >> https://mail.gnome.org/archives/release-team/2013-April/msg00038.html >> > > If you want to remove our shell accounts, please provide us with > an alternative way of publishing our tarballs (and do give us a heads > up on d-d-l before hand, so we can collect anything which we might > be keeping in our $(HOME) and $(HOME)/public_html). > As you can see from the subject of my e-mail at [1], the whole discussion is just a proposal at this moment of time, again just a proposal (it didn't go to d-d-l yet, cause we are still discussing all the possible solutions and the first step is usually hearing what the release-team has to say). I'm currently working with Olav Vitters to build a script that will work exactly as ftpadmin does now with a little but big difference: you'll be able to run it locally on your machine. (ideally you will have to rsync the tarball to the server and then install it as you currently do) This way we'll be able to disable logins to master.gnome.org but people will still be able to provide tarballs for their modules. Tools are evolving really fast and honestly I feel that the future will definitely see tarballs being dropped at some point. And that point is not close, I believe. Also as a side note, the logins to people.gnome.org *won't* be disabled, we are talking about logins to master.gnome.org now which is the only machine that has so many logins and ssh keys stored on the whole subsets of systems we host on the GNOME Infrastructure. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Some updates from the GNOME Sysadmin Team
Hello, some time has passed since my latest update so here we come with a few items I've been working on on the past two weeks. New infrastructure-announce mailing list --- >From the 8th of May a new mailing list has been started for all the announcements about downtimes, outages, maintenances related to the GNOME Infrastructure. As a side note the mail you are currently reading will be the last that will be kept CCed on desktop-devel-list and foundation-list. Please take a little minute to subscribe yourself to the new list at [1] to not loose any of the updates from the GNOME Sysadmin Team. --- Jabber --- As you may have noticed our Jabber server currently doesn't allow you to add any JID not equal to j...@jabber.gnome.org, that means you can't chat with people having a JID registered on a different server than the one hosted on the GNOME Infrastructure. The problem is related to a specific firewall port not being open, we've taken action on it and the relevant port will be open really soon for the clients to successfully "talk" with other clients coming from the "outside world". --- live.gnome.org --- Our wiki had a really quick maintenance [2] that upgraded it to the latest available MoinMoin's release. (1.9.7) This release takes in a stronger password encryption (it's not based on SHA anymore, but on PASSLIB instead), I would suggest anyone to change their password as soon as possible. In addition to the above, I've cleaned up a bit inactive users, deleted and trashed pages: 1. inactive users (users that registered but never did a single edit since the time they registered their account) were around 23000 (loads of spammers), the current amount of registered and active users went to 6000. Editing pages became really too slow, MoinMoin currently checks each of the registered user's subscriptions list for eventually notifying the user about the change that occurred on the page being edited. That process was taking around 9-10 seconds, and that was actually expected with an amount of 29000 registered users. 2. deleted pages (pages that were marked as 'Deleted' on the wiki) got moved from the data/ directory of live.gnome.org to a backup directory and the cache was cleaned for the changes to take place. 3. trashed pages (pages that were marked as 'Trashed' on the wiki) got moved from the data/ directory of live.gnome.org to a backup directory and the cache was cleaned for the changes to take place. --- MeetBot --- Our Services bot was enhanced with MeetBot, more details are available at [3]. Make good use of it! --- KGB Bot --- I've been working during the past week on the KGB Bot [4] (it has been a pain to package dozen of perl libraries!), which is a little IRC bot capable of sendind out notifications when a commit occurs on a specific git repository. I'm currently waiting the RH IT to open the specific port on the firewall for the kgb-client to communicate correctly with the bot which is hosted on a machine outside the datacenter where git.gnome.org runs. I'll make sure to send out an additional mail when the service is ready to go accepting new requests. That should be all for now, have an awesome weekend! [1] https://mail.gnome.org/mailman/listinfo/infrastructure-announce [2] https://mail.gnome.org/archives/foundation-list/2013-May/msg00033.html [3] https://mail.gnome.org/archives/foundation-list/2013-April/msg00037.html [4] http://kgb.alioth.debian.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Some updates from the GNOME Sysadmin Team
2013/5/17 Andrea Veri KGB Bot > --- > > I've been working during the past week on the KGB Bot [4] (it has been a > pain to package dozen of perl libraries!), which is a little IRC bot > capable of sendind out notifications when a commit occurs on a specific git > repository. I'm currently waiting the RH IT to open the specific port on > the firewall for the kgb-client to communicate correctly with the bot which > is hosted on a machine outside the datacenter where git.gnome.org runs. > I'll make sure to send out an additional mail when the service is ready to > go accepting new requests. > KGB Bot is finally ready to go, if you are interested in receiving commit notifications for a specific GNOME module on an IRC channel hosted at irc.gnome.org, please open a bug against the 'sysadmin' module on Bugzilla or directly mail me the relevant information: 1. repository-name 2. channel-name In addition to this, the Etherpad istance hosted by the GNOME Infrastructure is up and running at https://etherpad.gnome.org. The service is and will be restricted to all the GNOME teams that will request access to it (at the moment the Board, Release Team, Advisory Board, Marketing Team), if you are interested in the service please drop me an e-mail anytime. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Many services are being migrated to the new proxy setup: possible problems
Hi, we've been working over the past few days on migrating our web services to use our new proxy setup that will act as an intermediate host between the clients and the services themselves. A few issues have been reported in regard of Bugzilla and mails. Specifically a few users haven't been able to login correctly on Bugzilla. In addition mails haven't been flushing for a few hours, we've taken action already and the next MX records propagation should fix the issue. Please report us any issue either through Bugzilla itself by filing a bug against the sysadmin product or by getting in touch with us on #sysadmin at irc.gnome.org. Important note for all the users having access to the people.gnome.orgservice: the people.gnome.org's service has been moved the proxy, thus you won't be able to ssh into that machine correctly. Please use the 'webapps2.gnome.org' host instead. Thanks for your patience, Andrea ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
build.gnome.org: hardware issues
Hi, the machine that was currently hosting build.gnome.org went down the past thursday after an hardware problem, we're currently in touch with the manufacturer for having the relevant piece substituted as soon as possible. As a note, the 'No Route to Host' during git pushes is expected and related to this issue. One of the hooks is failing to connect to the build machine, thus failing. This won't affect git pushes or any other git activity. Please keep an eye at [1] for the next status updates. Thanks for your patience, [1] https://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Announcing GNOME's official GitHub mirror
2013/8/15 Michael Catanzaro > > On Thu, 2013-08-15 at 12:26 +0300, אנטולי קרסנר wrote: > > Hello, > > > > GitHub indeed offers many features that Gnome's git web interface > > doesn't. > > Yes, but we've disabled them all. I really fail to see the point of > GitHub without its killer feature (pull requests); it seems to have no > advantages over our current infrastructure. > Again, the point of the mirror is to encourage people that are on GitHub to contribute to the GNOME Project, how? By forking a specific repository and then following the usual procedure for having the patch reviewed and eventually accepted. We are not diverging (and we won't diverge) from our development workflow, I agree with you that leaving pull requests open can take in some confusion and we'll be trying to address that by adding the relevant wiki page [1] on the description of each of the repositories hosted on the mirror so that people are aware of that. In an ideal world we should just disable pull requests completely directly on Github, but that would require extra efforts from the Github's guys that did a lot to help us mirroring our source code. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Announcing GNOME's official GitHub mirror
Pressed sent too early. [1] https://wiki.gnome.org/Sysadmin/GitHub 2013/8/15 Andrea Veri > 2013/8/15 Michael Catanzaro > >> >> On Thu, 2013-08-15 at 12:26 +0300, אנטולי קרסנר wrote: >> > Hello, >> > >> > GitHub indeed offers many features that Gnome's git web interface >> > doesn't. >> >> Yes, but we've disabled them all. I really fail to see the point of >> GitHub without its killer feature (pull requests); it seems to have no >> advantages over our current infrastructure. >> > > Again, the point of the mirror is to encourage people that are on GitHub > to contribute to the GNOME Project, how? By forking a specific repository > and then following the usual procedure for having the patch reviewed and > eventually accepted. > > We are not diverging (and we won't diverge) from our development workflow, > I agree with you that leaving pull requests open can take in some confusion > and we'll be trying to address that by adding the relevant wiki page [1] on > the description of each of the repositories hosted on the mirror so that > people are aware of that. > > In an ideal world we should just disable pull requests completely directly > on Github, but that would require extra efforts from the Github's guys that > did a lot to help us mirroring our source code. > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Correct .doap file syntax for the tag
Hi, I noticed that many repositories are not using the tag correctly into the respective .doap files. The tag should possibly match the repository name (i.e gnome-shell.git --> gnome-shell, gnome-user-docs.git --> gnome-user-docs) for two main reasons: 1. everyone is aware of which specific module in git is being used for generating a specific release. (the ftpadmin scripts gets for generating a mail accordingly to be sent to ftp-release-list, so something like "Archive Manager" as won't help finding out where that specific release is being maintained at) 2. many other scripts are relying on matching the exact repository-name. Please take a little minute to update the .doap files accordingly in case your modules are not following the correct syntax. Thanks in advance, -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the tag
2013/8/21 Jens Georg > On Mi, 2013-08-21 at 00:15 +0200, Andrea Veri wrote: > > Hi, > > > > > > I noticed that many repositories are not using the tag > > correctly into the respective .doap files. The tag should > > possibly match the repository name (i.e gnome-shell.git --> > > gnome-shell, gnome-user-docs.git --> gnome-user-docs) for two main > > reasons: > > > > > > 1. everyone is aware of which specific module in git is being used for > > generating a specific release. (the ftpadmin scripts gets for > > generating a mail accordingly to be sent to ftp-release-list, so > > something like "Archive Manager" as won't help finding out > > where that specific release is being maintained at) > > > > > > 2. many other scripts are relying on matching the exact > > repository-name. > > Is this case-sensitive? > Yes, it is. :-) -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the tag
Thanks a lot David for working on this, the patch has been tested and was included into the relevant script. cheers, Andrea 2013/8/22 David King > On 2013-08-20 21:23, Shaun McCance wrote: > >> On Wed, 2013-08-21 at 00:15 +0200, Andrea Veri wrote: >> >>> I noticed that many repositories are not using the tag >>> correctly into the respective .doap files. The tag should >>> possibly match the repository name (i.e gnome-shell.git --> >>> gnome-shell, gnome-user-docs.git --> gnome-user-docs) for two main >>> reasons: >>> >> >> That's not how the rest of the world uses the name property. If you >> want the location of the repository, that's what the location property >> of the Repository class is for. Or use a custom property in our DOAP >> extension namespace. >> > > I just made a change to add the repository information to the Cheese DOAP > file: > > https://git.gnome.org/browse/**cheese/commit/?id=** > ba6f9e564cc828d197bf89a7d71e7e**a697fb3132<https://git.gnome.org/browse/cheese/commit/?id=ba6f9e564cc828d197bf89a7d71e7ea697fb3132> > > It is a few more lines than using the name property, but has the benefit > that other public clones of the repository have the upstream git location > included. > > Looking at the mirror script, it seems that using the DOAP name property > for the repository name can be avoided entirely. I filed a bug about this, > with a patch: > > https://bugzilla.gnome.org/**show_bug.cgi?id=706562<https://bugzilla.gnome.org/show_bug.cgi?id=706562> > > -- > http://amigadave.com/ > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Correct .doap file syntax for the tag
No, sorry for not pointing that out on my previous email, you can use a tag of your choice but it would be simply awesome to have all the tags in place. cheers, 2013/8/22 Debarshi Ray > On Wed, Aug 21, 2013 at 10:48:11AM +0200, Olav Vitters wrote: > > On Wed, Aug 21, 2013 at 12:15:32AM +0200, Andrea Veri wrote: > >> 2. many other scripts are relying on matching the exact > >> repository-name. > > > > Which ones? No script that I am aware of uses this to figure out the > > repository name. It uses https://git.gnome.org/repositories.doap, and > > that contains the real repository name. > > Now that David's patch [1] has been applied, is the requirement of having > the tag match the repository name still valid? Particularly if I > add to my modules's DOAP? > > Cheers, > Debarshi > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=706562 > > -- > Life is like bein' on a mule team. Unless you're the lead mule, all > the scenery looks about the same. > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
OUTAGE: Rack and network switch move, 24th September, 17 UTC
Hi, tomorrow, 24th September from 17 UTC (hopefully the move shouldn't take more than 2-3 hours) all our servers at the Phoenix2 datacenter will be migrated to a new rack and network switch. All the services *except* the following ones will be experiencing an outage: 1. www.gnome.org 2. www.guadec.org 3. IRC Services 4. l10n.gnome.org 5. ns-slave.gnome.org Unfortunately status.gnome.org will be offline as well during the migration, I'll make sure to keep everyone updated as soon as the machines will be coming up. Thanks for your patience and have an awesome day, -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: OUTAGE: Rack and network switch move, 24th September, 17 UTC
The migration of all our machines went just fine and the following actions were taken: 1. all machines are finally living on their own rack 2. all machines are finally using their own network switch 3. all machines have been configured for the sysadmin team to access both KVM / MGMT consoles. I'm sorry for the bad timing of this but we unfortunately didn't have the chance to decide when the change could happen given the on-site engineers were on the datacenter today after several weeks. I would like to thank everyone for the patience and wish everyone an awesome release day, 2013/9/23 Andrea Veri > Hi, > > tomorrow, 24th September from 17 UTC (hopefully the move shouldn't take > more than 2-3 hours) all our servers at the Phoenix2 datacenter will be > migrated to a new rack and network switch. > > All the services *except* the following ones will be experiencing an > outage: > > 1. www.gnome.org > 2. www.guadec.org > 3. IRC Services > 4. l10n.gnome.org > 5. ns-slave.gnome.org > > Unfortunately status.gnome.org will be offline as well during the > migration, I'll make sure to keep everyone updated as soon as the machines > will be coming up. > > Thanks for your patience and have an awesome day, > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Mass Reboot: Sunday 20th, 22:00 - 23:30 PM GMT+2
Hi, we'll be performing a mass reboot of all our machines this upcoming sunday to apply all the kernel and security updates. All the services will be affected for a few minutes until the machines reboot, please stay tuned for more updates from the Sysadmin Team and most of all keep an eye at [1], we'll make sure to update it as things move forward. Have an awesome day, [1] https://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Mass Reboot: Sunday 20th, 22:00 - 23:30 PM GMT+2
Hi, all the servers rebooted successfully except two machines (seems they are stuck at "Rebooting machine") that are actually going to be power-cycled as soon as the on-site personnel will phisically reach the machines given that (unfortunately) the PDUs for the two machines appear to be non-responsive to our logins. (a ticket has been opened to have this fixed asap as well) The machines affected are: 1. bugzilla 2. clipboard (ns-master.gnome.org and ldap.gnome.org, all the DNS requests are currently being served by our slave while SSSD is luckily caching all the logins to git.gnome.org, you might be experiecing slow git pushes though given sssd tries to ping ldap.gnome.org anyway) We'll be making sure that the machines will be power cycled as soon as possible to restore all the services. Thanks for your patience and as always keep an eye on [1]. [1] https://status.gnome.org 2013/10/16 Andrea Veri > Hi, > > we'll be performing a mass reboot of all our machines this upcoming sunday > to apply all the kernel and security updates. All the services will be > affected for a few minutes until the machines reboot, please stay tuned for > more updates from the Sysadmin Team and most of all keep an eye at [1], > we'll make sure to update it as things move forward. > > Have an awesome day, > > [1] https://status.gnome.org > > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Mass Reboot: Sunday 20th, 22:00 - 23:30 PM GMT+2
Status update: 1. bugzilla and clipboard are back up again and the services were restored just fine. 2. the manegement cards have been finally configured. (this allows us to reboot, power cycle, check the status of the hardware remotely) 3. mysqld's replication has been configured and will be finalized in the next few hours. 4. a bugzilla-backup node will be set up to avoid any downtime in the case vbox (the machine hosting bugzilla) will get in trouble. The GNOME Sysadmin team worked as much hard as it could to restore the services but most of all we would like to thank everyone for the usual patience and help you gave us reporting issues and contacting us when a problem occurred. Have an awesome day, 2013/10/21 Andrea Veri > Hi, > > all the servers rebooted successfully except two machines (seems they are > stuck at "Rebooting machine") that are actually going to be power-cycled as > soon as the on-site personnel will phisically reach the machines given that > (unfortunately) the PDUs for the two machines appear to be non-responsive > to our logins. (a ticket has been opened to have this fixed asap as well) > > The machines affected are: > > 1. bugzilla > 2. clipboard (ns-master.gnome.org and ldap.gnome.org, all the DNS > requests are currently being served by our slave while SSSD is luckily > caching all the logins to git.gnome.org, you might be experiecing slow > git pushes though given sssd tries to ping ldap.gnome.org anyway) > > We'll be making sure that the machines will be power cycled as soon as > possible to restore all the services. > > Thanks for your patience and as always keep an eye on [1]. > > [1] https://status.gnome.org > > > 2013/10/16 Andrea Veri > >> Hi, >> >> we'll be performing a mass reboot of all our machines this upcoming >> sunday to apply all the kernel and security updates. All the services will >> be affected for a few minutes until the machines reboot, please stay tuned >> for more updates from the Sysadmin Team and most of all keep an eye at [1], >> we'll make sure to update it as things move forward. >> >> Have an awesome day, >> >> [1] https://status.gnome.org >> >> >> -- >> Cheers, >> >> Andrea >> >> Debian Developer, >> Fedora / EPEL packager, >> GNOME Sysadmin, >> GNOME Foundation Membership & Elections Committee Chairman >> >> Homepage: http://www.gnome.org/~av >> > > > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
DNSSEC has been deployed on gnome.org
Hi,
the GNOME Sysadmin team worked hard recently to set up DNSSEC on the
gnome.org's DNS tree and we can finally say that both our major domains (
gnome.org, guadec.org) are currently being covered by DNSSEC successfully.
This actually means that you will be able to verify that the resources you
are viewing are really coming from the GNOME servers and not from any other
server in the middle between you and the GNOME servers themselves. (MITM
attack)
How can you verify you are really connecting to {git, master, webapps2}.
gnome.org? (with webapps2.gnome.org being the host you should be connecting
to for updating your people.gnome.org's webspace)
ssh -oVerifyHostKeyDNS=yes -v git.gnome.org
Or directly add the above parameter into your /etc/ssh/ssh_config file this
way:
VerifyHostKeyDNS=yes
And run 'ssh -v git.gnome.org', the result you should receive: (the same
procedure can be repeated with the other domains outlined above)
debug1: Server host key: RSA 00:39:fd:1a:a4:2c:6b:28:b8:2e:95:31:c2:90:72:03
debug1: found 1 secure fingerprints in DNS
debug1: matching host key fingerprint found in DNS
debug1: ssh_rsa_verify: signature correct
If you instead want to verify if gnome.org or guadec.org are being
correctly verified by your DNS resolver, use dig this way:
dig . DNSKEY | grep -Ev '^($|;)' > root.keys
dig +sigchase +trusted-key=./root.keys gnome.org. A | cat -n
The result you should see:
105 ;; WE HAVE MATERIAL, WE NOW DO VALIDATION
106 ;; VERIFYING DS RRset for org. with DNSKEY:59085: success
107 ;; OK We found DNSKEY (or more) to validate the RRset
108 ;; Ok, find a Trusted Key in the DNSKEY RRset: 59085
109 ;; Ok, find a Trusted Key in the DNSKEY RRset: 19036
110 ;; VERIFYING DNSKEY RRset for . with DNSKEY:19036: success
111
112 ;; Ok this DNSKEY is a Trusted Key, DNSSEC validation is ok: SUCCESS
We'll be working to move more domains over to DNSSEC in the near future.
Have an awesome day everyone!
--
Cheers,
Andrea
Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin,
GNOME Foundation Membership & Elections Committee Chairman
Homepage: http://www.gnome.org/~av
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Updates from the GNOME Sysadmin Team
2013/11/21 Ekaterina Gerasimova > On 21 November 2013 15:48, Andrea Veri wrote: > > 2. projects.gnome.org's migration to wiki.gnome.org. > > > > The projects.gnome.org website is currently being migrated to the > following > > places: > > > > GNOME Apps: https://wiki.gnome.org/Apps > > GNOME Projects: https://wiki.gnome.org/Projects > > > > Both pages are currently under construction. Maintainers and developers > will > > now be able to modify their app / project page without the need of a git > > account > > Don't all maintainers have to have a git account anyway? :) Not necessarily, someone might just be a random contributor that spots an error on the documentation and wants to fix it right away. Honestly speaking I'm loving this new look, pages are more readable now, with a new design, easier to maintain and modify by everyone having a Wiki account. Have you ever cloned the gnomeweb-wml repository yourself? It's around 600M in size :-) > > and most of all without the need to clone an huge repo like > > gnomeweb-wml. All these without losing some of the benefits of Git like > the > > history of previous changes and a diff between the various page changes > > themselves. > > When you document how to lock down individual pages to prevent random > people from from editing them, please send the link to the mailing > lists as it is moderately complicated if one has not done it before. > Sure, that can be done this way: 1. Create a page with the following syntax: 'SysadminGroup' 2. add a list of wiki usernames like https://wiki.gnome.org/SysadminGroup 3. add the ACL at the beginning of the wiki page you want to lock down: #acl WikiPageName/SysadminGroup:read,write,delete,admin,revert All:read Have an awesome day! -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Mass Reboot: Tuesday 3rd, 22:00 - 23:30 PM GMT+2
Hi, we'll be performing a mass reboot of all our machines this upcoming tuesday to apply all the kernel and security updates. All the services will be affected for a few minutes until the machines reboot, please stay tuned for more updates from the Sysadmin Team and most of all keep an eye at [1], we'll make sure to update it as things move forward. Have an awesome day, [1] https://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Mass Reboot: Tuesday 3rd, 22:00 - 23:30 PM GMT+2
All the reboots went fine except for socket.gnome.org (hosting www.gnome.organd www.guadec.org) that had a power failure. On-site personnel is working on the issue already. Please keep an eye on the status website [1] for further updates on this matter. cheers, Andrea [1] https://status.gnome.org 2013/11/28 Andrea Veri > Hi, > > we'll be performing a mass reboot of all our machines this upcoming > tuesday to apply all the kernel and security updates. All the services will > be affected for a few minutes until the machines reboot, please stay tuned > for more updates from the Sysadmin Team and most of all keep an eye at [1], > we'll make sure to update it as things move forward. > > Have an awesome day, > > [1] https://status.gnome.org > > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Updates from the GNOME Sysadmin Team: New Mirroring service, Owncloud 6
Howdy, it's time for yet another round of updates from the GNOME Sysadmin Team. This time it's not about future maintenances or outages but about our completely new mirroring service. As you may have been aware of GNOME has a lot of mirrors around the world but we never took advantage of them and kept using our main mirror kindly served by the Academic Computer Club of the Umea University. (ftp.acc.umu.sebeing a CNAME to ftp.gnome.org) Many mirrors contacted me and the team in the past asking if keeping their mirror around was worth the disk space they were using for our project given the very low amount of downloads they were receiving. (that was expected given download.gnome.org was a plain redirect to ftp.gnome.org, and thus to ftp.acc.umu.se) I personally always answered yes, it was worth keeping the GNOME code synced in as much places in the world as possible but at the same time I felt that we needed a proper mirroring infrastructure to properly serve the downloads through all the mirrors that decided to provide disk space and bandwitdh to support our project. Looking around and thanks to an Olav Vitter's review we decided to move forward and setup a Mirrorbrain [1] istance. You can read more about its features at [2]. After a few days spent making the EPEL packages (Thanks Patrick for the work you put on reviewing and accepting them!), configuring and tweaking, our istance is finally live at [3]. As you will see we have plenty of mirrors based in EU and just one in the US and Asia. I'll be contacting a few mirrors in those zones and eventually welcome them as new GNOME mirrors so we can have our downloads served in the fastest way possible even in remote regions like Australia, Asia and the US itself. (if anyone knows someone interested in mirroring GNOME sources, please redirect the request to supp...@gnome.org) Gving a look at a new indexing table we've introduced on the file indexes of our main mirror can be a good way to get started to how Mirrorbrain works behind the scenes. [4] Obviously all the links that existed before Mirrorbrain are still working just fine but the great difference are them now being served through Mirrorbrain (which then redirects the user to the closest mirror through mod_geoip) itself and SSL. Another good way of testing the whole setup out is by using curl, this way: 'curl -iS https://download.gnome.org/sources/gnome-terminal/3.11/gnome-terminal-3.11.0.tar.xz.mirrorlist ' --- Owncloud release 6 The other update I wanted to report is our Owncloud istance [5] being upgraded to the very latest release being Owncloud 6. As usual please redirect account requests to me or to supp...@gnome.org directly as explained at [6]. [1] http://mirrorbrain.org/ [2] http://mirrorbrain.org/features/ [3] https://download.gnome.org/ [4] https://download.gnome.org/sources/gnome-terminal/3.11/gnome-terminal-3.11.0.tar.xz.mirrorlist [5] http://cloud.gnome.org/ [6] https://wiki.gnome.org/Sysadmin/Owncloud -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Updates from the GNOME Sysadmin Team: New Mirroring service, Owncloud 6
2013/12/12 Dominique Leuenberger a.k.a. Dimstar > > There might be something not entirely setup yet. Looking at this I get 11 > Mirrors as option, but all of them returned with the same Prio (100) > > looking at for example http://download.opensuse.org/distribution/13.1/iso/ > openSUSE-13.1-Addon-NonOss-BiArch-i586-x86_64.iso.mirrorlist (also based > on MirrorBrain) the provided mirrors are clearly differently prioritized. > > Might be worthy to have a look at this. > Thanks for noticing Dominique, mirrors priorities (Prio) should be actually tweaked when, for example, a specific mirror (it being on the same country of the user requesting the file) has more bandwidth or reliability than another and we might want to prefer a redirect to that specific mirror which has more chances to serve the file in the fastest way as possible. That said given I didn't yet have time to investigate the provided bandwidth for each of the mirrors we use, keeping Prio at 100 for each of the mirrors will actually result in MirrorBrain randomly selecting one of the closest mirrors to your area even if that specific mirror has a lower bandwidth than another one close to you. We might want to tweak this parameter a bit as soon as I find the time to get more stats about what our mirrors are providing in terms of bandwidth speed. Thanks again for reporting and have an awesome day! (/me added a note accordingly) -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Mass Reboot: Thursday 9th, 20:00 - 21:30 PM GMT+1
Hi, we'll be performing a mass reboot of all our machines this upcoming thursday to apply all the kernel and security updates. All the services will be affected for a few minutes until the machines reboot, please stay tuned for more updates from the Sysadmin Team and most of all keep an eye at [1], we'll make sure to update it as things move forward. Have an awesome day, [1] https://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Mass Reboot: Thursday 9th, 20:00 - 21:30 PM GMT+1
All the reboots went fine, the GNOME Sysadmin Team wishes everyone a happy new year and an awesome day! cheers, Andrea 2014/1/7 Andrea Veri > Hi, > > we'll be performing a mass reboot of all our machines this upcoming > thursday to apply all the kernel and security updates. All the services > will be affected for a few minutes until the machines reboot, please stay > tuned for more updates from the Sysadmin Team and most of all keep an eye > at [1], we'll make sure to update it as things move forward. > > Have an awesome day, > > [1] https://status.gnome.org > > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
OUTAGE: Network switches move, 12th February, 10 - 11 UTC
Hi,
the engineers will be on-site for performing a switch move today, 12th
February. Several services will be unavailable for a few minutes until we
make the needed changes on the network configuration. The services affected:
1. jabber.gnome.org
2. blogs.gnome.org
3. {help,developer}.gnome.org
4. master.gnome.org
5. wiki.gnome.org
6. smtp.gnome.org
7. extensions.gnome.org
8. people.gnome.org
9. etherpad.gnome.org
10. proxy02.gnome.org
We'll work hard to restore all the services as soon as we can. As usual
I'll follow-up this email with an update.
Thanks for your patience.
--
Cheers,
Andrea
Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin,
GNOME Foundation Membership & Elections Committee Chairman
Homepage: http://www.gnome.org/~av
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: OUTAGE: Network switches move, 12th February, 10 - 11 UTC
The maintenance didn't go as expected and multiple issues arised, but the
machines are now back in production. Most probably tomorrow late afternoon
(18-19 UTC, or as soon as our engineer will be on-site again) we'll perform
another little outage to finally deal with the remaining items.
Thanks for your patience and please bear with us until we get the whole
move sorted out.
2014-02-12 18:17 GMT+01:00 Andrea Veri :
> Hi,
>
> the engineers will be on-site for performing a switch move today, 12th
> February. Several services will be unavailable for a few minutes until we
> make the needed changes on the network configuration. The services affected:
>
> 1. jabber.gnome.org
> 2. blogs.gnome.org
> 3. {help,developer}.gnome.org
> 4. master.gnome.org
> 5. wiki.gnome.org
> 6. smtp.gnome.org
> 7. extensions.gnome.org
> 8. people.gnome.org
> 9. etherpad.gnome.org
> 10. proxy02.gnome.org
>
> We'll work hard to restore all the services as soon as we can. As usual
> I'll follow-up this email with an update.
>
> Thanks for your patience.
>
> --
> Cheers,
>
> Andrea
>
> Debian Developer,
> Fedora / EPEL packager,
> GNOME Sysadmin,
> GNOME Foundation Membership & Elections Committee Chairman
>
> Homepage: http://www.gnome.org/~av
>
--
Cheers,
Andrea
Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin,
GNOME Foundation Membership & Elections Committee Chairman
Homepage: http://www.gnome.org/~av
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: OUTAGE: Network switches move, 12th February, 10 - 11 UTC
The outage has finally ended and all the machines are back up. Thanks for
your patience.
We'll be moving status.gnome.org to an external-hosted service to avoid it
being unavailable during wider maintenances.
Have an awesome day!
2014-02-13 3:35 GMT+01:00 Andrea Veri :
> The maintenance didn't go as expected and multiple issues arised, but the
> machines are now back in production. Most probably tomorrow late afternoon
> (18-19 UTC, or as soon as our engineer will be on-site again) we'll perform
> another little outage to finally deal with the remaining items.
>
> Thanks for your patience and please bear with us until we get the whole
> move sorted out.
>
>
> 2014-02-12 18:17 GMT+01:00 Andrea Veri :
>
> Hi,
>>
>> the engineers will be on-site for performing a switch move today, 12th
>> February. Several services will be unavailable for a few minutes until we
>> make the needed changes on the network configuration. The services affected:
>>
>> 1. jabber.gnome.org
>> 2. blogs.gnome.org
>> 3. {help,developer}.gnome.org
>> 4. master.gnome.org
>> 5. wiki.gnome.org
>> 6. smtp.gnome.org
>> 7. extensions.gnome.org
>> 8. people.gnome.org
>> 9. etherpad.gnome.org
>> 10. proxy02.gnome.org
>>
>> We'll work hard to restore all the services as soon as we can. As usual
>> I'll follow-up this email with an update.
>>
>> Thanks for your patience.
>>
>> --
>> Cheers,
>>
>> Andrea
>>
>> Debian Developer,
>> Fedora / EPEL packager,
>> GNOME Sysadmin,
>> GNOME Foundation Membership & Elections Committee Chairman
>>
>> Homepage: http://www.gnome.org/~av
>>
>
>
>
> --
> Cheers,
>
> Andrea
>
> Debian Developer,
> Fedora / EPEL packager,
> GNOME Sysadmin,
> GNOME Foundation Membership & Elections Committee Chairman
>
> Homepage: http://www.gnome.org/~av
>
--
Cheers,
Andrea
Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin,
GNOME Foundation Membership & Elections Committee Chairman
Homepage: http://www.gnome.org/~av
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Databases migration: Wednesday, 19th February 2014, 9:00 - 11:00 AM, CET
Hi, a maintenance is planned for this upcoming wednesday for us to finalize the databases migration, the services affected during the two-hours downtime: 1. bugzilla.gnome.org 2. blogs.gnome.org 3. cloud.gnome.org 4. etherpad.gnome.org 5. jabber.gnome.org We'll make sure to update [1] as things will move forward. [1] http://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Databases migration: Wednesday, 19th February 2014, 9:00 - 11:00 AM, CET
The following services have been restored: 1. blogs.gnome.org 2. cloud.gnome.org 3. etherpad.gnome.org 4. jabber.gnome.org bugzilla.gnome.org had a database corruption on one of its tables, a repair is currently in progress. Will send another update soon. 2014-02-18 0:42 GMT+01:00 Andrea Veri : > Hi, > > a maintenance is planned for this upcoming wednesday for us to finalize > the databases migration, the services affected during the two-hours > downtime: > > 1. bugzilla.gnome.org > 2. blogs.gnome.org > 3. cloud.gnome.org > 4. etherpad.gnome.org > 5. jabber.gnome.org > > We'll make sure to update [1] as things will move forward. > > > [1] http://status.gnome.org > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Databases migration: Wednesday, 19th February 2014, 9:00 - 11:00 AM, CET
bugzilla.gnome.org should be up and running again and the faulty table has been repaired. Thanks for your patience, Andrea 2014-02-19 11:20 GMT+01:00 Andrea Veri : > The following services have been restored: > > 1. blogs.gnome.org > 2. cloud.gnome.org > 3. etherpad.gnome.org > 4. jabber.gnome.org > > bugzilla.gnome.org had a database corruption on one of its tables, a > repair is currently in progress. Will send another update soon. > > > 2014-02-18 0:42 GMT+01:00 Andrea Veri : > > Hi, >> >> a maintenance is planned for this upcoming wednesday for us to finalize >> the databases migration, the services affected during the two-hours >> downtime: >> >> 1. bugzilla.gnome.org >> 2. blogs.gnome.org >> 3. cloud.gnome.org >> 4. etherpad.gnome.org >> 5. jabber.gnome.org >> >> We'll make sure to update [1] as things will move forward. >> >> >> [1] http://status.gnome.org >> >> -- >> Cheers, >> >> Andrea >> >> Debian Developer, >> Fedora / EPEL packager, >> GNOME Sysadmin, >> GNOME Foundation Membership & Elections Committee Chairman >> >> Homepage: http://www.gnome.org/~av >> > > > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Sysadmin, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Inactive accounts (git, master) cleanup
Hi, the GNOME Sysadmin Team has recently reviewed its LDAP account policies and moved forward creating an automatized way to cleanup inactive accounts. Specifically our cleanup script will work this way: 1. it parses the gnome_pushlog files for the whole set of Git repositories hosted at git.gnome.org. A gnome_pushlog file contains the following information: a. the username of the user that succesfully pushed to that repository b. the timestamp of the push 2. it compares all the timestamps against a two-years timeline. 3. it removes the inactive accounts from the gnomecvs (git.gnome.org's access) and ftpbasic groups. (master.gnome.org's access) As you may have understood every user that does not commit a single time (on any of the hosted repositories) within two years has its account removed from both the gnomecvs and ftpbasic groups. In the case the account's owner is back and willing to get the commit access back an email to should be sent. At this point an existing maintainer should approve the request and the account will eventually be reinstated. I would also like to remember everyone to give an additional look at the various DOAP files: keeping them up-to-date is essential given maintainers are enabled to provide Git access to external contributors, thus leaving an old or inactive maintainer on the DOAP file of your project may result in approval mails being sent to the wrong people delaying the approval of the account and thus the consequent account creation. Additional reading about security and the GNOME Infrastructure can be found on the gnome-i18n in relation of the new way of committing translations directly from the l10n.gnome.org's web interface. [1] Have an awesome day! [1] https://mail.gnome.org/archives/gnome-i18n/2014-March/msg00148.html -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Mass Reboot: Monday 31th of March, 21:30 - 23:00 PM CET
Hi, we'll be performing a mass reboot of all our machines this upcoming monday to apply all the kernel and security updates. All the services will be affected for a few minutes until the machines reboot, please stay tuned for more updates from the Sysadmin Team and most of all keep an eye at [1], we'll make sure to update it as things move forward. Have an awesome day, [1] https://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Mass Reboot: Monday 31th of March, 21:30 - 23:00 PM CET
On Fri, 28 Mar 2014, Andrea Veri wrote: > we'll be performing a mass reboot of all our machines this upcoming > monday to apply all the kernel and security updates. All the > services will be affected for a few minutes until the machines reboot, > please stay tuned for more updates from the Sysadmin Team and most of > all keep an eye at [1], we'll make sure to update it as things move > forward. All the machines were rebooted and the services are currently back. Thanks for your patience and have an awesome day! -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
OpenSSL's Heartbleed security bug status report
Hi, as you might know about a severe security vulnerability was found on the OpenSSL package earlier. [1] (CVE-2014-0160) The GNOME Sysadmin Team acted on it and applied the relevant security update on every single machine hosted. Additionally all the previous SSL certificates were revoked and replaced by a new set of certificates. If you are running any SSL-related plugin on your browser you'll surely be warned the SSL certificates for the following domains have changed during the past 24 hours: 1. *.gnome.org 2. *.guadec.org 3. *.gimp.org That said I would still suggest everyone to update their passwords (on any of the hosted services used before today) in case the private keys were compromised and the user password was sent and captured by the attacker using the Heartbleed bug. Sessions on the hosted services have also been cleared. Have an awesome day everyone and please mail in case of problems. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: OpenSSL's Heartbleed security bug status report
On Wed, 09 Apr 2014, Andrea Veri wrote: > Have an awesome day everyone and please mail org> in case of problems. Issues like (Error code: sec_error_ocsp_unknown_cert) on Firefox should be fixed within 24 hours from now, our CA has a delay between 1 to 24 hours before the new certificates being acked as valid. You can temporary bypass this issue by disabling the OCSP check on your Firefox's preferences. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Mass Reboot: Monday 19th of May, 21.00 - 22.00 CET
Hi, we'll be performing a mass reboot of all our machines this upcoming monday to apply all the kernel and security updates. All the services will be affected for a few minutes until the machines reboot, please stay tuned for more updates from the Sysadmin Team and most of all keep an eye at [1], we'll make sure to update it as things move forward. We'll also take the time during the reboots to switch our current storage away from our current main NFS node to the brand new GlusterFS nodes. This should not affect the reboots planned downtime. Have an awesome day and thanks for your attention! [1] http://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Mass Reboot: Monday 19th of May, 21.00 - 22.00 CET
On Sat, 17 May 2014, Andrea Veri wrote: > We'll also take the time during the reboots to switch our current > storage away from our current main NFS node to the brand new GlusterFS > nodes. This should not affect the reboots planned downtime. The maintenance took a bit more due to rsync taking its good time to transfer the missing files from our old NFS server to the two new GlusterFS volumes. Thanks for your patience and please report any issue you may find to the GNOME Sysadmin Team. [1] Have a good day! [1] https://wiki.gnome.org/Sysadmin/Contact -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
SCHEDULED MAINTENANCE: 30th May, 00:00 - 01:00 CET
Hi, we'll be performing a little maintenance this night (CET TZ) to move our main mount points away from NFS to the Gluster native client. This will help our data to failover automatically to the other configured storage in case of failures. [1] The move should not affect any service but we feel having a one hour window for the maintenance will help us performing the move without rushing in case of issues during the remounts. Thanks for your patience! -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: SCHEDULED MAINTENANCE: 30th May, 00:00 - 01:00 CET
Woops, I did. [1] [1] https://mail.gnome.org/archives/infrastructure-announce/2014-May/msg2.html 2014-05-29 21:28 GMT+02:00 Hashem Nasarat : > Did you miss a [1]? > > On 05/29/2014 03:19 PM, Andrea Veri wrote: > > Hi, > > > > we'll be performing a little maintenance this night (CET TZ) to move our > > main mount points away from NFS to the Gluster native client. This will > > help our data to failover automatically to the other configured storage > > in case of failures. [1] > > > > The move should not affect any service but we feel having a one hour > > window for the maintenance will help us performing the move without > > rushing in case of issues during the remounts. > > > > Thanks for your patience! > > > > -- > > Cheers, > > > > Andrea > > > > Debian Developer, > > Fedora / EPEL packager, > > GNOME Sysadmin, > > GNOME Foundation Membership & Elections Committee Chairman > > > > Homepage: http://www.gnome.org/~av > > > > > > ___ > > foundation-list mailing list > > foundation-l...@gnome.org > > https://mail.gnome.org/mailman/listinfo/foundation-list > > > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GUADEC 2014 registration is now open!
The GUADEC organization team is happy to announce the availability of the registration form [1] for the upcoming GUADEC to be held in Strasbourg, France at Epitech, a software engineer school in the heart of the city, is glad to welcome our community and host the venue [2] for the event! This year we are going to include a list of participants to the event online at [3]. Once registered to the event do not forget we also provide a set of badges [4] you can use to share on your website! Let everyone know you are coming to such a great event held in one of the most beautiful cities of Europe! About GUADEC The GNOME Users And Developers European Conference (GUADEC), is an annual conference taking place in Europe, whose prime topic is the development of the GNOME desktop environment which sees many participants from all over the world. [1] https://www.guadec.org/register [2] https://www.guadec.org/venue [3] https://www.guadec.org/participant-list [4] https://www.guadec.org/media -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors member, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Mass Reboot: Sunday 17th of August, 21.30 - 23.00 CET
Hi, we'll be performing a mass reboot of all our machines this upcoming sunday to apply all the kernel and security updates. All the services will be affected for a few minutes until the machines reboot, please stay tuned for more updates from the Sysadmin Team and most of all keep an eye at [1], we'll make sure to update it as things move forward. Have an awesome day and thanks for your attention! [1] http://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors member, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
PLANNED MAINTENANCE: Tuesday 07th of October, 9 AM - 12 PM
Hi, this upcoming tuesday we'll be performing a maintenance on all the hosted machines, what is planned: 1. mass reboot to apply latest security updates 2. switch to the new authentication system based on FreeIPA As usual keep an eye at [1] and stay tuned on Planet GNOME for a blog post with all the details and instructions from one of the most significative changes we have ever planned on our infrastructure. [1] http://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors member, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
The GNOME Infrastructure is now powered by FreeIPA!
As preannounced at [1] the GNOME Infrastructure switched to a new
Account Management System which is reachable at https://account.gnome.org.
All the details will follow.
Introduction
--
It's been a while since someone actually touched the underlaying
authentication infrastructure that powers the GNOME machines. The very
first setup was originally configured by Jonathan Blandford (jrb) who
configured an OpenLDAP istance with several customized schemas.
(pServer fields in the old CVS days, pubAuthorizedKeys and GNOME
modules related fields in recent times)
While OpenLDAP-server was living on the GNOME machine called clipboard
(aka ldap.gnome.org) the clients were configured to synchronize users,
groups, passwords through the nslcd daemon. After several years Jeff
Schroeder joined the Sysadmin Team and during one cold evening (date
is Tue, February 1st 2011) spent some time configuring SSSD to replace
the nslcd daemon which was missing one of the most important SSSD
features: caching. What surely convinced Jeff to adopt SSSD (a very
new but promising sofware at that time as the first release happened
right before 2010's Christmas) and as the commit log also states ("New
sssd module for ldap information caching") was SSSD's caching feature.
It was enough for a certain user to log in once and the
'/var/lib/sss/db' directory was populated with its login information
preventing the LDAP daemon in charge of picking up login details (from
the LDAP server) to query the LDAP server itself every single time a
request was made against it. This feature has definitely helped in
many occasions especially when the LDAP server was down for a
particular reason and sysadmins needed to access a specific machine or
service: without SSSD this wasn't ever going to work and sysadmins
were probably going to be locked out from the machines they were used
to manage. (except if you still had '/etc/passwd', '/etc/group' and
'/etc/shadow' entries as fallback)
Things were working just fine except for a few downsides that appeared
later on:
1. the web interface (view) on our LDAP user database was managed by
Mango, an outdated tool which many wanted to rewrite in Django
that slowly became a huge dinosaur nobody ever wanted to look into again
2. the Foundation membership information were managed through a MySQL
database, so two databases, two sets of users unrelated to each other
3. users were not able to modify their own account information on
their own but even a single e-mail change required them to mail
the GNOME Accounts Team which was then going to authenticate their request
and finally update the account.
Today's infrastructure changes are here to finally say the issues
outlined at (1, 2, 3) are now fixed.
What has changed?
--
The GNOME Infrastructure is now powered by Red Hat's FreeIPA which
bundles several FOSS softwares into one big "bundle" all surrounded by
an easy and intuitive web UI that will help users update their account
information on their own without the need of the Accounts Team or any
other administrative entity. Users will also find two custom fields on
their "Overview" page, these being "Foundation Member since" and "Last
Renewed on date". As you may have understood already we finally
managed to migrate the Foundation membership database into LDAP itself
to store the information we want once and for all. As a side note it
might be possible that some users that were Foundation members in the
past won't find any detail stored on the Foundation fields outlined
above. That is actually expected as we were able to migrate all the
current and old Foundation members that had an LDAP account registered
at the time of the migration. If that's your case and you still would
like the information to be stored on the new setup please get in
contact with the Membership Committee at stating so.
Where can I get my first login credentials?
--
Let's make a little distinction between users that previously had
access to Mango (usually maintainers) and users that didn't. If you
were used to access Mango before you should be able to login on the
new Account Management System by entering your GNOME username and the
password you were used to use for loggin in into Mango. (after loggin
in the very first time you will be prompted to update your password,
please choose a strong password as this account will be unique across
all the GNOME Infrastructure)
If you never had access to Mango, you lost your password or the first
time you read the word Mango on this post you thought "why is he
talking about a fruit now?" you should be able to reset it by using
the following command:
ssh -l yourgnomeuserid account.gnome.org
The command will start an SSH connection between you and
account.gnome.org, once authenticated (with the SSH key you previously
had registered on our Infrastructure) you will trigger a command that
will
Re: The GNOME Infrastructure is now powered by FreeIPA!
2014-10-10 22:57 GMT+02:00 Sébastien Wilmet : > Hi, > > Thank you for the migration! > > On Tue, Oct 07, 2014 at 11:28:44AM +0200, Andrea Veri wrote: >> If you are interested in receiving or keeping using your >> people.gnome.org's webspace please mail >> stating so. > > Why not documenting how to access people.gnome.org on the wiki? So all > people that already have a personal web space can keep using it. > > (I've asked for a people.gnome.org web space this monday, so of course > I'm still interested in using it..). There you go. [1] The page has been added as a link at [2]. [1] https://wiki.gnome.org/AccountsTeam/AccessingPersonalWebspace [2] https://wiki.gnome.org/AccountsTeam/NewAccounts -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors member, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: The GNOME Infrastructure is now powered by FreeIPA!
2014-10-11 2:14 GMT+02:00 Alexandre Franke : > On Fri, Oct 10, 2014 at 10:57 PM, Sébastien Wilmet wrote: >> On Tue, Oct 07, 2014 at 11:28:44AM +0200, Andrea Veri wrote: >>> If you are interested in receiving or keeping using your >>> people.gnome.org's webspace please mail >>> stating so. >> >> Why not documenting how to access people.gnome.org on the wiki? So all >> people that already have a personal web space can keep using it. >> >> (I've asked for a people.gnome.org web space this monday, so of course >> I'm still interested in using it..). > > Now that we have an owncloud instance, there's an overlap. Is there > still a good reason to keep using people.g.o instead of owncloud? The Owncloud istance is currently only available to Foundation members while theoretically anyone with a Git / Master account with a good rationale can request access to people.gnome.org. I personally still find scping a file to my public_html directory faster and easier when I have a file or two to share on the fly. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors member, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
MASS REBOOT: Saturday 18th of October, 10 AM - 11 AM CET
Hello, we'll be rebooting all the machines this upcoming saturday morning to apply RHEL 6.6's updates. The time window will be around 2-3 minutes of downtime per service. As usual keep an eye at: https://status.gnome.org As a side note, this will be my latest maintenance announcement e-mail to both desktop-devel-list and foundation-list as I'll be primarily using infrastructure-announce [1] for such announcements from now on after transitioning to it a few months ago. If you didn't already, please subscribe to that list to not lose any maintenance, outage announcements. Have a nice day! [1] https://mail.gnome.org/mailman/listinfo/infrastructure-announce -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors member, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: java-atk-wrapper maintainership
2014-10-17 18:43 GMT+02:00 David King : > As Alejandro is the maintainer, you should ask him, rather than > desktop-devel-list, if you want to become a maintainer. Well, this statement is half right in my opinion for one main reason: e-mails exchanged between Magdalen and Alejandro are most probably going to stay private forever so no one would have been aware of a maintainer change, you would just have seen a commit with 'Update DOAP file' as its subject and that's all but the context and the possible discussions between the two interested parties was going to live on their mailboxes forever. When a maintainer change is discussed it's *always* the best thing to do CCing desktop-devel-list so that everyone is aware, a backlog is kept and all the maintainers can express their opinion in case the request is made by someone who has not the requirements to fill such position. So I'm totally in favor of making these announcements / requests / discussions public, encouraging the use of private mail exchanges is just wrong and may lead to confusing situations with no real benefit for either the involved parties nor our community. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors member, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Bugzilla upgrade to release 4.4.6 - Testing needed
Hi there! I'm so glad to announce we made a tremendous jump ahead of having our Bugzilla istance upgraded to the latest stable release being 4.4.6. Thanks to the hard job of Krzesimir Nowak who spent the last few months migrating our customizations to the new codebase and to Olav Vitters who started the process a while back we are ready to announce the availability of a test istance based on Bugzilla 4.4.6 with all the customizations we have in place at bugzilla.gnome.org. Although have tested and are not aware of any blockers are still around to justify delaying the upgrade even longer we thought it was the case to give everyone a week for testing all the new features and GNOME customizations, specifically we would love receiving intensive testing on the following features: 1. Git-bz 2. Patch statuses extension (i.e [1]) 3. Splinter --- Warnings: --- Playing with patch statuses or attachments themselves will result in an ERR_CERT_COMMON_NAME_INVALID error which you can safely mark as safe and keep browsing the page you were looking for. The error will go away when we'll switch the SSL certificates to the ones we have in production. (the error is currently there as our proxies do have a wildcard certificate for the gnome.org domain which will only cover third-level subdomains and result in an error when used on fourth-level subdomains like in this case (bug%bugid.bugzilla-test-attachments.gnome.org)) If you'll be looking at [2] you'll see no weekly bug summary has been published, collectstats has run et all but the dump we used is around one month old so no, no stats are expected to be there on purpose. The weekly-bug-summary however supports the use of the "days" URL parameter. [3] --- Where is the test istance located? --- The test istance is located at https://bugzilla-test.gnome.org. The database is hosted on the same machine with all the limitations this may have, please don't overload the machine with huge queries. --- How do I report a bug I found? --- Please report all bugs at [4] making sure a [4.4] prefix is appended before the summary text --- How long will you keep the testing istance up before upgrading the production database? --- The testing istance will be kept up from today 15th to the 22th of January, so exactly one week from today. After this period if no blocker bugs have been reported bugzilla.gnome.org will be undergoing a 36 to 48 hours maintenance and the production database will be upgraded. [1] https://bugzilla-test.gnome.org/attachment.cgi?id=201923&action=edit [2] https://bugzilla-test.gnome.org/page.cgi?id=weekly-bug-summary.html [3] https://bugzilla-test.gnome.org/page.cgi?id=weekly-bug-summary.html&days=60 [4] https://bugzilla.gnome.org/enter_bug.cgi?product=bugzilla.gnome.org&short_desc=%5B4.4%5D%20 -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Bugzilla upgrade to release 4.4.6 - Testing needed
And two more details I missed: --- How can I login? --- If you didn't change your password between today and the 2014-12-08, your login will succeed by using the same login information as bugzilla.gnome.org. --- Can I update bugs without annoying people with e-mail notifications? --- Yes, you can. Currently e-mail notifications are disabled from the test instance so no one is going to receive a single notification from your actions. The database in use will be trashed when the testing week will end and the move to production will take place. cheers, 2015-01-15 19:46 GMT+01:00 Andrea Veri : > Hi there! > > I'm so glad to announce we made a tremendous jump ahead of having our > Bugzilla istance upgraded to the latest stable release being 4.4.6. > > Thanks to the hard job of Krzesimir Nowak who spent the last few > months migrating our customizations to the new codebase and to Olav > Vitters who started the process a while back we are ready to announce > the availability of a test istance based on Bugzilla 4.4.6 with all > the customizations we have in place at bugzilla.gnome.org. > > Although have tested and are not aware of any blockers are still > around to justify delaying the upgrade even longer we thought it was > the case to give everyone a week for testing all the new features and > GNOME customizations, specifically we would love receiving intensive > testing on the following features: > > 1. Git-bz > 2. Patch statuses extension (i.e [1]) > 3. Splinter > > --- > Warnings: > --- > > Playing with patch statuses or attachments themselves will result in > an ERR_CERT_COMMON_NAME_INVALID error which you can safely mark as > safe and keep browsing the page you were looking for. The error will > go away when we'll switch the SSL certificates to the ones we have in > production. (the error is currently there as our proxies do have a > wildcard certificate for the gnome.org domain which will only cover > third-level subdomains and result in an error when used on > fourth-level subdomains like in this case > (bug%bugid.bugzilla-test-attachments.gnome.org)) > > If you'll be looking at [2] you'll see no weekly bug summary has been > published, collectstats has run et all but the dump we used is around > one month old so no, no stats are expected to be there on purpose. The > weekly-bug-summary however supports the use of the "days" URL > parameter. [3] > > --- > Where is the test istance located? > --- > > The test istance is located at https://bugzilla-test.gnome.org. The > database is hosted on the same machine with all the limitations this > may have, please don't overload the machine with huge queries. > > --- > How do I report a bug I found? > --- > > Please report all bugs at [4] making sure a [4.4] prefix is appended > before the summary text > > --- > How long will you keep the testing istance up before upgrading the > production database? > --- > > The testing istance will be kept up from today 15th to the 22th of > January, so exactly one week from today. After this period if no > blocker bugs have been reported bugzilla.gnome.org will be undergoing > a 36 to 48 hours maintenance and the production database will be > upgraded. > > [1] https://bugzilla-test.gnome.org/attachment.cgi?id=201923&action=edit > [2] https://bugzilla-test.gnome.org/page.cgi?id=weekly-bug-summary.html > [3] > https://bugzilla-test.gnome.org/page.cgi?id=weekly-bug-summary.html&days=60 > [4] > https://bugzilla.gnome.org/enter_bug.cgi?product=bugzilla.gnome.org&short_desc=%5B4.4%5D%20 > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Infrastructure Team Coordinator, > GNOME Foundation Board of Directors Secretary, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: OUTAGE: bugzilla.gnome.org, 09th February (09:00 CET) - 10th February (22:00 CET)
The upgrade has been finalized and the machine is back to production. A special thank you goes to Andre Klapper and Krzesimir Nowak for their hard work to make this happen. We are also happy to announce Krzesimir has joined the GNOME Bugmasters team and admin status has been granted to him on bugzilla.gnome.org. We are also delighted about the fact today's upgrade has given a new life to the Bugmasters team: new members are joining and more are willing to participate to the team and most of all old members are back on track to provide their valuable feedback and expertise. While we are confident enough testing was made we welcome everyone to submit bugs that may arise at [1]. Have an awesome evening everyone! [1] https://bugzilla.gnome.org/enter_bug.cgi?product=bugzilla.gnome.org 2015-02-04 20:22 GMT+01:00 Andrea Veri : > Hi, > > this upcoming monday we'll be performing bugzilla.gnome.org's upgrade > to the very latest Bugzilla release, it being 4.4.8. > > The upgrade time frame has been kept wide enough for us to perform the > following operations: > > 1. Make sure the Bugzilla database is replicated on our MySQLd replica > (mainly dumping the DB and restoring it on the replica so they are > both in sync. We need all the tables to be on READ LOCK while doing > this so the upgrade is a good time for the replication of this > database to be restored) > 2. Perform the upgrade itself from release 3.4 to release 4.4.8 > 3. Perform post-upgrade maintenance operations > > More information about what happened behind the scenes during these > months can be found at [1]. > > As usual keep an eye at [2], we'll make sure to update it with ETAs as > things move forward. > > [1] http://krnowak.blogspot.it/2015/01/gnome-bugzilla-upgrade.html > [2] https://status.gnome.org > > -- > Cheers, > > Andrea > > Debian Developer, > Fedora / EPEL packager, > GNOME Infrastructure Team Coordinator, > GNOME Foundation Board of Directors Secretary, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GIMPNet / irc.gnome.org: enhancements for the end users and migration to a new ircd, call for public testing
GNOME Community, the GIMPNet Operators Team and the GNOME Sysadmin Team have been working together recently to finally migrate the IRC network they manage to a newer ircd with enhanced features (such as SSL) and proper IRC services (Nickserv, Chanserv). We are proud to announce the network is finally ready for public testing. Please read on if you are interested in participating on its launch. The new network is currently composed by 6 servers and another one (irc.poop.nl) will join its ranks soon: irctest0.acc.umu.se irctest2.acc.umu.se irctest3.acc.umu.se irctest4.acc.umu.se irc.eagle.y.se irc.gimp.ca Connecting to any of these servers can be done on the following ports: 6668 (non-ssl port) 6697 (SSL port) An irc-test.gnome.org and irc-test.gimp.org DNS entries have also been added to the gnome.org and gimp.org DNS zone files. You can safely connect to one of them and your client will do the rest. Servers are using a certificate having one DN (currently being the FQDN of the host) so connecting to one of the two DNS entries above with SSL verification turned on will result in an error as the DN won't match. That is expected, in case you are willing to verify the SSL certificate (on XChat make sure the 'Accept invalid certificate' flag is not set, on irssi make sure '-ssl -ssl_verify' is appended to your connect command) make sure to connect to a single server on the list above with the proper flags set. The Operators Team is currently evaluating whether the network can be moved under one main wildcard certificate (in the form of irc[0-9].gimp.org). Once connected, make sure to register your nickname by querying NickServ. A 'help' command can be issued to NickServ when a query window has been created. The 'help' will provide you the needed information for succesfully registering your nickname. If you are a GNOME module maintainer or you lead a certain team or group and are interested in registering a channel through ChanServ please do so. The same 'help' command output provided by ChanServ will provide you the appropriate syntax for registering your channel. Please DO NOT abuse the registration of new channels and please get in touch with the Operators Team for requesting the cancellation of a registered channel / nickname in case an abuse has happened. Your points of contact for reporting issues or other related queries are: #opers, for a direct chat with the Operators Team https://bugzilla.gnome.org/enter_bug.cgi?product=sysadmin&component=IRC, for reporting a bug at GNOME's Bugzilla A few more details about the new network we are introducing: 1. It might definitely happen for your client to connect to the network through the SSL port and ending up on an empty channel. Don't be scared as that's expected as in most cases the ircd runs on the same server as the current production network. Note the current production network is not SSL-capable. 2. Most of the servers (while just irc.poop.nl was in the past) are now IPv6-capable. 3. All nicks and channels registered during the public testing will be kept. 4. Another announcement will follow when we will be close to switch over to the new network. The announcement will have all the references and details for you to properly migrate your client to the new network. 5. The public testing duration is expected to be 2 weeks and unless any critical issue arises we will move forward and perform the switch over to the new network. See point 4. on this regard. IRC plays an important role on the communications of the GNOME Project and allows every single GNOME contributor, developer or user to get in touch with the GNOME community as a whole and we totally believe the new network we've been building will improve the way you were used to manage your nickname, your channels and your privacy thanks to the newly introduced SSL capability. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Current status of the GNOME Github mirror
Hey, more than half a year has passed since the GNOME Github mirror was setup and we are incredibly happy that it has contributed positively to bring more contributors to the GNOME Project. While new contributors joined the GNOME community and started contributing through the usual workflow of submitting patches to Bugzilla many more made use of Pull Requests (PRs) which we explicitly requested not to use on the description of the mirror itself [1]. It's clear PRs might be seen as a handy and straightforward way to contribute code or documentation to a specific GNOME module especially for contributors that aren't familiar with GNOME's procedures of submitting patches. On this matter I contacted the Github team asking whether it was possible to remove PRs on our specific organization. Unfortunately at this moment of time there's no simple way for that to happen. Apparently we don't have a simple solution we could apply to solve the problem all together but the ideal way to start limiting the waste of contributions and patches on Github would be shipping a CONTRIBUTING.md file on each of the hosted repositories. Creating such file will automatically create a warning when the user will try to open a PR against one of the modules. An example of what the CONTRIBUTING.md file should contain: """The GNOME contributing guidelines do require patches to be forwarded to GNOME's Bugzilla instance hosted at https://bugzilla.gnome.org, as such please do not open Pull Requests (PRs) against any of the modules under the GNOME organization as they will be ignored. More information is available at the following wiki page: https://wiki.gnome.org/Sysadmin/GitHub"""; That said, I would like to invite anyone interested to include the sample file above on the module/s they contribute to. If you have a different opinion on how this should be managed, please follow up to this thread. Have an awesome day! [1] https://wiki.gnome.org/Sysadmin/GitHub -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Current status of the GNOME Github mirror
2015-05-06 8:41 GMT+02:00 Philip Withnall : > We could have a CONTRIBUTING.md which suggests that bug _discussion_ > happens in Bugzilla, I guess. This is definitely a good point. Accepting pull requests is not bad per se as many people might see having yet another account in Bugzilla as enough to not contribute at all. What I've seen though, especially on the ostree case, has been Github being used for the entire workflow: from the submit of the patches themselves, the discussions behind them, any possible proposed change and the final push to git.gnome.org. This is totally fine but goes further ahead from the original scope of the mirror. The idea we had in mind when we launched it was to make our code available to a vast majority of users. We introduced a FAQ with all the possible ways to contribute but we didn't take into account we couldn't disable PRs on our organization as the feature is still not available on the Github hosting platform. Contributions of any kind and sent to Github should not be wasted and contributors encouraged. At the same time we should make sure our workflow and contributing guidelines are respected. After hearing your opinions I would take the following actions: 1. Introduce a CONTRIBUTING.md file with the following text* for all the repositories except the ones that don't want to be affected. (opt-out) 2. Make use of Bugzilla for discussing patches further than a single "Thanks for your contribution, patch has been merged" message 3. Allow maintainers to close PRs if the code has been merged already (thanks Bastien!). If a patch is straightforward to apply and it's fine for the maintainer to go ahead why asking the contributor to attach it to Bugzilla? This might just discourage the user and the contribution will get lost. I still have to find out a way to map maintainers with their Github account as it probably differs in many cases from their respective GNOME handle. As said we don't want contributors and contributions to get lost so having interested maintainers looking and being notified by Github PRs is definitely a way to accomplish the above. * """The GNOME contributing guidelines require patches to be forwarded to GNOME's Bugzilla instance hosted at https://bugzilla.gnome.org. Please do not open GitHub pull requests against this module as they will be ignored. More information is available at the following wiki page: https://wiki.gnome.org/Sysadmin/GitHub"""; -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Network switch for irc.gnome.org: Thursday, 14th May, 2015, 22 - 23 CET+1
Dear GNOME Community, after testing the new IRCD and its integration with services (ChanServ, NickServ) [1] we are delighted to announce we will be moving the testing servers to production this upcoming thursday from 22 to 23 CET+1. The downtime should not take more than a few minutes: old ircds will be shutdown and the new ones will be restarted for properly binding to the default ports. (being 6667 for non-ssl connections and 6697 for ssl-enabled connections) The new network will come with new features: - SSL (reachable by connecting to port 6697 on each of the servers hosted within the network) - IRC services (ChanServ, NickServ), that will allow you to register your nickname and channel in a safe and straightforward way. Instructions on how to interact with services are available at [1], [2] will receive a revamp in the next couple of days including all the details and support contacts - Improved IPv6 support now available on both irc.acc.umu.se and irc.poop.nl As a side note the GNOME Bot known as 'Services' will be removed from channels that previously requested it unless a specific team requires its MeetBot capability. I'll give [3] a look and see which teams made use of it in the past years and leave it connected on those channels. If you want the bot to join a new channel as you would be willing to manage a meeting through it opening a bug at [4] should be the ideal way for having it added to the requested channel. The Operators Team will be available on the #opers channel during and after the migration, questions and support requests should be redirected to that channel. This is the list of servers that will populate the network: - irc.acc.umu.se: IPv4: 130.239.18.215, IPv6: 2001:6b0:e:2018::215 - irc.eagle.y.se, IPv4: 82.99.16.155 - irc.gimp.ca, IPv4: 142.4.222.129 - irc.poop.nl, IPv4: 83.98.201.42 - IPv6: 2001:16f8:4::42 The irc.gimp.org (the record irc.gnome.org points to) round robin will be updated with the new IPs on the same day, it might take a few hours for all the DNS resolvers to get in sync, in case make use of the IPs of the machines to connect as listed above. As usual keep an eye at [5]. [1] https://mail.gnome.org/archives/gnome-announce-list/2015-April/msg00010.html [2] https://wiki.gnome.org/Sysadmin/IRC [3] https://meetbot.gnome.org/ [4] https://bugzilla.gnome.org/enter_bug.cgi?product=sysadmin&component=IRC [5] https://status.gnome.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin Team Coordinator, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av signature.asc Description: Digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Mailman Upgrade: Wednesday 23th of November, 09:00 - 10:00 CET
Hi, tomorrow we'll be performing a minor version upgrade of our Mailman instance, specifically from release 2.1.15 to release 2.1.23 [1]. The following services won't be reachable (mails will be kept in the queue and flushed as soon as the upgrade has happened) during the maintenance: 1. mail.gnome.org The upgrade has been specifically scheduled to resolve the mass un-subscriptions a few list owners have been reporting since the time Yahoo and AOL (and any other DMARC aware domain) have decided to enforce DMARC policies. On this side there will be two user visible changes: 1. the From address will be modified (From: Andrea Veri ) 2. the Reply-To header will be modified as well (Reply-To: , 3. the first and second point will be true only for the senders behind a domain that has a DMARC policy published on the DNS (it being reject or quarantine or none. Mailman makes a call against the DNS resolvers and looks for a DMARC record for the target domain) This particular option can be overridden on a per-list basis with the following values [3]: 1. Reject 2. Discard As usual please keep an eye at [2]. Have a great day, [1] http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/NEWS [2] https://status.gnome.org [3] https://wiki.list.org/DEV/DMARC -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Github's pull requests and GNOME
Hello, one of the most problematic points we've been discussing since the GNOME Github mirror was introduced [1] (three years already!) has been the presence of pull requests and the missing feature / functionality to actually turn them off for specific repositories / organizations. What many have correctly pointed out during these three years relates to the fact pull requests and our current contributions workflow collide in a way that has caused confusion between community members with dozens of patches being left on Github unreviewed. Finally the GNOME Infrastructure Team is going to introduce a daily cronjob (first run is scheduled next week, enough time for collecting excludes) that will close all the pull requests for each repository hosted under the GNOME organization umbrella. The closure message will look like this: """ Thank you for contributing to $project_name! $project_name uses Bugzilla for code review. If you have never contributed to GNOME before make sure you have read the getting started documentation: http://www.gnome.org/get-involved Otherwise please visit https://wiki.gnome.org/Newcomers/CodeContributionWorkflow and follow the instructions there to upload your change to Bugzilla. """ If you don't want the script to actually run against any of your maintained products, modules, components please drop me an e-mail and I'll make sure proper excludes will be set. Thanks, [1] https://mail.gnome.org/archives/foundation-list/2013-August/msg00010.html -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Github's pull requests and GNOME
Hey, added nevimer on the excludes list, your permissions to that repository have been granted. cheers, 2016-12-05 15:01 GMT+01:00 Hubert Figuière : > On 29/11/16 10:00 AM, Andrea Veri wrote: > >> Finally the GNOME Infrastructure Team is going to introduce a daily >> cronjob (first run is scheduled next week, enough time for collecting >> excludes) that will close all the pull requests for each repository >> hosted under the GNOME organization umbrella. The closure message will >> look like this: > > > How does one mark the PR as "don't close" ? I was working with a new > contributor in a PR that I would have taken to merge the usual > non-github way. But now the cronjob has closed it. Can't reopen it... > > This is the PR: >https://github.com/GNOME/nemiver/pull/2 > > Maybe the cronjob should check whether there was activity from more than > one person and act on that. > >> If you don't want the script to actually run against any of your >> maintained products, modules, components please drop me an e-mail and >> I'll make sure proper excludes will be set. > > Given that I'm not the official maintainer at all for the module. Just > MITMing contributions... > Can we have it reopen? Can I be granted permissions to do so ? (username > on github is @hfiguiere) > > Thanks, > > Hub > -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Interested community members @ domains ownership
@membership: The following set of domains is about to expire in less than 60 days and the Board of Directors confirmed there's no real interest in these renewals as the projects that were behind them are inactive / dead since several years now: gnomejournal.org tomboy-online.com tomboy-online.org If you have any interest in them please get in touch with me directly. Thanks! -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Bugzilla migration tool user accounts
Sure, just please coordinate with me when the migrations are going to start. cheers, 2017-12-01 9:31 GMT+01:00 Carlos Soriano : > Yes, I believe we can stop that on our end. Andrea? Can we stop mails coming > from GitLab for a specific product for when we do bug migrations? > > > Best > -- > Carlos Soriano > GNOME Foundation > Treasurer, Board of Directors > > On Fri, Dec 1, 2017 at 6:18 AM, wrote: >> >> On Thu, Nov 30, 2017 at 9:51 AM Nicolas Dufresne >> wrote: >>> >>> Le jeudi 30 novembre 2017 à 12:54 +0100, Alexandre Franke a écrit : >>> > On Thu, Nov 30, 2017 at 6:43 AM, wrote: >>> > > Bastien, do you also mean to imply that the wish to be subscribed >>> > > to >2000 >>> > > issues means that receiving >2000 mails won't be a problem? >>> > >>> > It will be a problem, but not as bad as losing subscription on those >>> > issues. It would still be very much worth looking for a way to >>> > temporarily disable notifications to avoid that flood. I can also >>> > imagine that sending that many email out at once can raise some flags >>> > and make GNOME look bad in the eye of some email providers. >>> >>> This was an issue when some project tried to migrate to Phabricator. >>> The server end up stalled for days, spamming everyone. We need to be >>> careful. >> >> >> Carlos thought it would be possible to just stop all email while a >> migration was running; it sounds like that's what we should plan to do. >> >> Regards, >> Philip C >> >> ___ >> desktop-devel-list mailing list >> desktop-devel-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/desktop-devel-list > > -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Planned MAJOR OUTAGE: Thursday 08th of February, 17:00 - 19:00 UTC
Hi, this upcoming Thursday we'll be performing a rack migration for *all* the GNOME Infrastructure machines hosted in PHX2, the services that will see a one to two hours downtime are: wiki.gnome.org smtp.gnome.org mail.gnome.org git.gnome.org gitlab.gnome.org bugzilla.gnome.org www.gnome.org extensions.gnome.org sdk.gnome.org cloud.gnome.org pentagon.gimp.org (hosting all GIMP/GTK main websites) paste.gnome.org download.gnome.org blogs.gnome.org master.gnome.org jabber.gnome.org help.gnome.org developer.gnome.org planet*.gnome.* vote.gnome.org api.gnome.org *.guadec.org The GNOME Infrastructure team and Red Hat NOC will make sure the downtime will be minimized as much as possible. Once the machines have been migrated we'll move forward with service validations. As usual please keep an eye at [1] for status updates. Thanks! [1] https://status.gnome.org -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Planned MAJOR OUTAGE: Thursday 08th of February, 17:00 - 19:00 UTC
While the move was overall successful one of the hosts has been found having an hardware failure and requires its mainboard to be replaced. The part will be replaced today between 14 - 15 UTC. The affected services that will have a downtime are: bugzilla.gnome.org paste.gnome.org etherpad.gnome.org id.gnome.org opw.gnome.org Thanks, 2018-02-05 12:04 GMT+01:00 Andrea Veri : > Hi, > > this upcoming Thursday we'll be performing a rack migration for *all* > the GNOME Infrastructure machines hosted in PHX2, the services that > will see a one to two hours downtime are: > > wiki.gnome.org > smtp.gnome.org > mail.gnome.org > git.gnome.org > gitlab.gnome.org > bugzilla.gnome.org > www.gnome.org > extensions.gnome.org > sdk.gnome.org > cloud.gnome.org > pentagon.gimp.org (hosting all GIMP/GTK main websites) > paste.gnome.org > download.gnome.org > blogs.gnome.org > master.gnome.org > jabber.gnome.org > help.gnome.org > developer.gnome.org > planet*.gnome.* > vote.gnome.org > api.gnome.org > *.guadec.org > > > The GNOME Infrastructure team and Red Hat NOC will make sure the > downtime will be minimized as much as possible. Once the machines have > been migrated we'll move forward with service validations. As usual > please keep an eye at [1] for status updates. > > Thanks! > > [1] https://status.gnome.org > > > -- > Cheers, > > Andrea > > Red Hatter, > Fedora / EPEL packager, > GNOME Infrastructure Team Coordinator, > Former GNOME Foundation Board of Directors Secretary, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
people.gnome.org SSH public key change
Hey, we recently rebuild the node that was running people.gnome.org and as such the SSH public keys for the host changed. The SSHFP entries have been updated to reflect this. Thanks! -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
gitlab-test.gnome.org decommission
Hey, we'll be deprecating and removing the gitlab-test instance to free up some resources from one of the hypervisors we manage. If there's anyone interested in keeping it active please let me know so we can keep it around for some more. If not I'll be removing the VM next Tuesday 17th of July. Thanks, -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gitlab-test.gnome.org decommission
The gitlab-test.g.o instance has been decommissioned successfully. cheers, 2018-07-10 12:36 GMT+02:00 Andrea Veri : > Hey, > > we'll be deprecating and removing the gitlab-test instance to free up > some resources from one of the hypervisors we manage. If there's > anyone interested in keeping it active please let me know so we can > keep it around for some more. If not I'll be removing the VM next > Tuesday 17th of July. > > Thanks, > > -- > Cheers, > > Andrea > > Red Hatter, > Fedora / EPEL packager, > GNOME Infrastructure Team Coordinator, > Former GNOME Foundation Board of Directors Secretary, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: http://www.gnome.org/~av -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
git.gnome.org being discontinued: Thursday 23th of August
Hey, with GNOME finalizing the move to GitLab back at the end of May it's time to retire the former git.gnome.org service. The service will be shutdown next week on Thursday 23th of August. What will we shutdown? Mainly the git:// and ssh:// protocols. All the developers that accessed git.gnome.org in the past 7 days have been mailed accordingly. What will we keep around for backwards compatibility? The git.gnome.org vhost and its rewrites against the gitlab.gnome.org service. If you're using jhbuild make sure you remove any reference to the git:// and ssh:// protocols against git.gnome.org. Thanks and at your disposition for additional questions! -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
projects-old.gnome.org being discontinued
Hey, the projects-old website [1] was decided to be left around in 2013 right after transitioning projects pages to the GNOME's wiki (projects.g.o is a vhost that contains a set of redirects since then) for a short period of time while the transition was happening. I believe it's now a good time (after 5+ years!) to retire the former website all together. We'll be removing the vhost and the associated DNS entry on Friday 7th of December. If there's anyone interested in keeping it active please let me know so we can keep it around for some additional time, the code behind it is available on GitLab [2]. Thanks, [1] https://projects-old.gnome.org [2] https://gitlab.gnome.org/Archive/gnomeweb-wml -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: projects-old.gnome.org being discontinued
Liam, no, I really meant projects-old.gnome.org which as I described on my original e-mail was the pre-2013 projects page we had running before transitioning to the new wiki.g.o based projects listing. I believe the future of projects.g.o will vary, certain maintainers are setting up GitLab pages for their project (using Jekyll / Hugo), some others are using the wiki, still. I believe the engagement team was looking into possible new ways to unify projects listing into one single view, not sure what's the status there though. cheers, Il giorno mer 5 dic 2018 alle ore 21:10 Liam R E Quin ha scritto: > > On Wed, 2018-12-05 at 11:22 +0100, Andrea Veri wrote: > > Hey, > > > > the projects-old website [1] was decided to be left around in 2013 > > right after transitioning projects pages to the GNOME's wiki > > (projects.g.o is a vhost that contains a set of redirects since then) > > i think you mean projects.gnome.org, right? > > That seems to be a lot less complete, and also just has project names > and not explanations. So there's (out of date) information being lost. > > There are also a lot of external links to the page, so you'll break a > lot of links (and, for what it's worth, hurt gnome.org's search ranking > a little in the process). But this could be mitigated with an HTTP > redirect to a page telling people how to find what they might have > wanted. > > > for a short period of time while the transition was happening. I > > believe it's now a good time (after 5+ years!) to retire the former > > website all together. > > > If it goes, it might be helpful to add short descriptions to > projects.gnome.org, although that would mean a bunch of work of course. > The (current) wiki pages are not organized enough to make this a > question of easy scraping so maybe the answer is to automate something > that grabs the page title from the linked pages, and encourage project > maintaners to edit their wiki pages as needed? > > On the other hand it's fun exploring the page to find out what things > are :) > > The new page is much better overall, even without descriptions, because > of the division into categories. > > Liam (irc::ankh) > > > -- > Liam Quin - web slave for https://www.fromoldbooks.org/ > with fabulous vintage art and fascinating texts to read. > Click here to have the slave beaten. > -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: projects-old.gnome.org being discontinued
Liam, thanks for your comments, an additional note: this is actually NOT the old page as in theory whenever we'll have a new way of handling projects views the former (and to be considered old) website is going to be [1]. In 2013 we migrated several of those links to what projects.gnome.org is today and left projects-old un-maintained (individual maintainers were taking care of maintaining their own projects) which led to multiple of those links to become obsolete / historical (pre 2010) / not relevant anymore. Do you see any value in keeping those URLs around even if they're historical and not relevant since several years? cheers, [1] https://projects.gnome.org Il giorno gio 6 dic 2018 alle ore 22:23 Liam R E Quin ha scritto: > > On Thu, 2018-12-06 at 12:31 +0100, Andrea Veri wrote: > > Liam, > > > > no, I really meant projects-old.gnome.org which as I described on my > > original e-mail was the pre-2013 projects page we had running before > > transitioning to the new wiki.g.o based projects listing. > > Yes, i understood that. Sorry if i wasn't clear. > > > I believe the engagement team was looking > > into possible new ways to unify projects listing into one single > > view, not sure what's the status there though. > > Then i'd suggest holding off until you know, because redirecting the > old page to a new mechanism would make the most sense. As i said, > there's lots of links to projects-old.gnome.org. > > Liam > > > > > cheers, > > Il giorno mer 5 dic 2018 alle ore 21:10 Liam R E Quin > > ha scritto: > > > On Wed, 2018-12-05 at 11:22 +0100, Andrea Veri wrote: > > > > Hey, > > > > > > > > the projects-old website [1] was decided to be left around in > > > > 2013 > > > > right after transitioning projects pages to the GNOME's wiki > > > > (projects.g.o is a vhost that contains a set of redirects since > > > > then) > > > > > > i think you mean projects.gnome.org, right? > > > > > > That seems to be a lot less complete, and also just has project > > > names > > > and not explanations. So there's (out of date) information being > > > lost. > > > > > > There are also a lot of external links to the page, so you'll break > > > a > > > lot of links (and, for what it's worth, hurt gnome.org's search > > > ranking > > > a little in the process). But this could be mitigated with an HTTP > > > redirect to a page telling people how to find what they might have > > > wanted. > > > > > > > for a short period of time while the transition was happening. I > > > > believe it's now a good time (after 5+ years!) to retire the > > > > former > > > > website all together. > > > > > > If it goes, it might be helpful to add short descriptions to > > > projects.gnome.org, although that would mean a bunch of work of > > > course. > > > The (current) wiki pages are not organized enough to make this a > > > question of easy scraping so maybe the answer is to automate > > > something > > > that grabs the page title from the linked pages, and encourage > > > project > > > maintaners to edit their wiki pages as needed? > > > > > > On the other hand it's fun exploring the page to find out what > > > things > > > are :) > > > > > > The new page is much better overall, even without descriptions, > > > because > > > of the division into categories. > > > > > > Liam (irc::ankh) > > > > > > > > > -- > > > Liam Quin - web slave for https://www.fromoldbooks.org/ > > > with fabulous vintage art and fascinating texts to read. > > > Click here to have the slave beaten. > > > > > > > > -- > Liam Quin - web slave for https://www.fromoldbooks.org/ > with fabulous vintage art and fascinating texts to read. > Click here to have the slave beaten. > -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
[GitLab] Mass inactive / fake / spammy users cleanup
Hey, we recently performed a mass cleanup of 4155 users which include: 1. Users that never logged in after registering their account 2. Users that created an account, logged in once but never logged back in since then BUT never performed any kind of activity 3. Spammy users (which we select by looking at the bio, website_url fields which most of the times contain urls to external spam websites) This is a 2nd run of cleanups after the initial cleanup we ran back in March 2019 [1]. Thanks, [1] https://mail.gnome.org/archives/desktop-devel-list/2019-March/msg00019.html -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Contacting the Accounts Team changes
Hello! as everyone is well aware the only way you had to contact the GNOME Accounts Team till now was to mail accou...@gnome.org. Given the willingness to decommission RT (Request Tracker) and consolidate the reporting of issues and requests of support against GitLab we're happy to announce you can now request a new account or an update to an existing one directly via GitLab using pre-built templates. [1] has been updated accordingly. Thanks and available if you need further assistance. [1] https://wiki.gnome.org/AccountsTeam/NewAccounts -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
people.gnome.org host migration
Hi, the people.gnome.org has been migrated from webapps2 to palette, SSHFP entries have been updated accordingly. On a side note, you should be able to connect to the host by using people.gnome.org as the FQDN as the service is not living behind a proxy anymore. If you had an older .ssh/config entry pointing to webapps2, please remove it in addition to dropping any old people.g.o entry you had on .ssh/hosts. At your disposition in case of further questions, thanks! -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
New GNOME Account password reset tool is live!
Contributors, the GNOME Infrastructure is making available a new web based tool that will help you resetting your account password in case it was lost. As many of you know, the current way of updating your password was running a command on your terminal making sure your SSH key was up-to-date with the one we have on our systems. That was creating a barrier to contributors which aren't comfortable using a terminal, SSH or other developer oriented toolings. The new solution will ease the process and remove the need of utilizing a console and/or owning an SSH key. You can access the new tool at: https://password.gnome.org Documentation [1] has been updated to reflect this change as well. For any issue with the service, please open an issue at [2]. Thanks! [1] https://wiki.gnome.org/Infrastructure/RetrieveYourGNOMEAccountPassword [2] https://gitlab.gnome.org/Infrastructure/password-resets/-/issues/new P.S the former password reset method (`ssh -l username account.gnome.org`) has been removed/deprecated -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: New GNOME Account password reset tool is live!
Allan, that's correct, SSH keys are not a requirement anymore when requesting Foundation membership or a GNOME Account. I made sure the GitLab form for new membership applications [1] and GNOME Accounts [2] also reflects this. Thanks and please let me know whether I missed anything on the templates! [1] https://gitlab.gnome.org/Teams/MembershipCommittee/-/issues/new?issuable_template=membership-application [2] https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/new?issuable_template=new-account Il giorno mar 24 nov 2020 alle ore 11:54 Allan Day ha scritto: > Andrea Veri wrote: > ... > > the GNOME Infrastructure is making available a new web based tool that > will help you resetting your account password in case it was lost. As many > of you know, the current way of updating your password was running a > command on your terminal making sure your SSH key was up-to-date with the > one we have on our systems. That was creating a barrier to contributors > which aren't comfortable using a terminal, SSH or other developer oriented > toolings. The new solution will ease the process and remove the need of > utilizing a console and/or owning an SSH key. > > Awesome! Will this allow us to phase out SSH keys for LDAP accounts > and foundation memberships? (I thought I'd filed a ticket for that but > may have dreamt it.) > > Allan > -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Planned maintenance: Thursday 28th of January, 12:00 - 13.30 PM UTC
Hello, here to report we'll be having a maintenance / planned outage of all GNOME services during the 12:00 - 13:30 PM UTC time frame this upcoming Thursday due to code upgrades and switches reboots against our networking infrastructure. Given the nature of this maintenance and the fact we heavily use network based storage for VM and OSCP workloads, all services will be shutdown to avoid filesystem corruptions. Please keep an eye at https://status.gnome.org to know when services will be fully operational. Thanks! -- Cheers, Andrea Red Hatter, Fedora / EPEL packager, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Intent to retire people.gnome.org (31th of March)
Foundation members, developers, contributors, We've analyzed people.gnome.org usage over the course of 2021 and Q1 2022 and the actual results did not surprise us given the multitude of ways hosting a tarball or a simple file contributors have these days (GitLab pages, download.gnome.org, GitLab release for non-official builds, Openshift). What we found is the service being heavily utilized by a single contributor with around 18 other contributors utilizing the service every few months. With that in mind and unless anyone within the community objects with a good rationale we'll be retiring the service by the 31th of March. Thanks, -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://people.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Intent to retire people.gnome.org (31th of March)
Michael, Adding redirects once the service is down is a viable option, you can push those images to static.g.o and we can add a redirect afterwards to make sure stuff won't break. Let me know whether that works for you, thanks! On Wed, 9 Mar 2022 at 18:02 Michael Catanzaro wrote: > On Wed, Mar 9 2022 at 05:44:04 PM +0100, Andrea Veri > wrote: > > With that in mind and unless anyone within the community objects with > > a good rationale we'll be retiring the service by the 31th of March. > > Sadly I have images for appstream metadata hosted here (seemed like a > good idea back in 2014, oops), meaning once it goes down, older > releases will no longer display images in GNOME Software if distros > rebuild their appstream metadata. Potentially affected apps: > five-or-more, four-in-a-row, gnome-calculator, gnome-chess, > gnome-klotski, gnome-mahjongg, gnome-mines, gnome-nibbles, > gnome-robots, gnome-sudoku, gnome-taquin, gnome-tetravex, hitori, > iagno, lightsoff, quadrapassel, swell-foop, tali. These images are very > stale, so hopefully some apps have refreshed their images since I > created them, but the rest will break. I'll go through them all soon > and migrate all images to GitLab to ensure that GNOME 42 releases will > be OK, but of course there is no way to fix older releases. > > I also had a bunch of tarballs hosted here too, but it looks like > release team is no longer using them due to infrastructure > improvements, so that's no problem. > > Michael > > > -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://people.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Intent to retire people.gnome.org (31th of March)
Michael, That's lovely, thank you. I'll make sure those redirects will be there before retiring the service at the end of March. Il giorno ven 11 mar 2022 alle ore 22:26 Michael Catanzaro < mcatanz...@gnome.org> ha scritto: > Hi Andrea, I've pushed all the screenshots here: > > > https://gitlab.gnome.org/Infrastructure/static-web/-/commit/d205056a93ab19e53afbb1fe53310d71d7f0afd1 > > so it should be easy to set up a redirect now. I've also submitted MRs > to all affected apps to transition them from using the people.gnome.org > URLs to using GitLab instead. > > Michael > > > -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://people.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
master.gnome.org updated its SSH host keys
Hi, master.gnome.org was recently rebuilt and old SSH host keys were deprecated. The next time you attempt to log in you'll be warned host keys have effectively changed, please make sure to remove former keys under .ssh/known_hosts and retry. SSHFP records have been updated accordingly. Please get in touch if anything doesn't work the way it should. Thanks, -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.dragonsreach.it ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME Accounts - Introducing Automation
Hello, As we discussed during GUADEC and as many of you know, processing new and existing GNOME account changes has been a manual action for many years now. With the introduction of OCP, GitLab CI/CD, IPA and SSO, we wanted to enable GNOME contributors and developers to fulfil their needs in total autonomy and freedom without requiring interventions from our side when it came to provision resources or build/test GNOME software. With that in mind we're happy to announce new and existing GNOME account changes are now processed via automation. How it works --- When visiting [1] you will be shown an issue template composed of some documentation on top and a json dictionary. The only field that requires an update is the json dictionary, the following format should be used: action can be any of: 1. new_account 2. git_access 3. master_access 4. update_email While the module key should be the name of any GNOME module as found within [2], the module key should only be specified with the new_account, git_access, master_access actions. The title of the issue should be: "Account request". Other key takes when selecting the new_account action: 1. Your name, surname and username will be computed out of your full name as found in your GitLab profile 2. The registered email on your account will be the one of your GitLab profile Other key takes when selecting the update_email action: 1. The email that will be synchronized with IPA is the primary one you have registered on your GitLab account, please make sure that one is up-to-date What automation will take care of: 1. Generate your account information and allow the Accounts team to verify compliance, also add necessary labels 2. Mail individual existing GNOME module maintainers and have them acknowledge your new or existing GNOME account request 3. Once all the verifications have happened, automation will create your account or update it with additional permissions 4. Close the issue and turn the confidential flag to on once the full process has completed Please let us know any feedback you may have, for any bug report please use [3]. Once an initial phase of testing has happened, the idea we have is introducing the same automation within the GNOME Foundation Membership Committee as well during the coming months. Thanks! [1] https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/new?issuable_template=account-request [2] https://gitlab.gnome.org/GNOME [3] https://gitlab.gnome.org/Infrastructure/Infrastructure/issues -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.dragonsreach.it ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME Accounts - Introducing Automation
As a follow-up we had on Discourse there's a few more key takes I wanted to mention: 1. The git_access action mainly verifies you’re actively contributing to a GNOME module and the module maintainer is willing to grant you access to the LDAP group responsible for providing read-write capabilities within the entire set of GNOME’s GitLab namespace hosted repositories. DOAP files only control who maintains a module, for committers we mainly have one single LDAP group which in turn maps to a GitLab group where everyone is allowed to commit to any repository within GNOME’s GitLab namespace. This is the former "gnomecvs" group. 2. master_access has been renamed to maint_access, documentation has been updated. It effectively grants the ftpadmin role, the reason why we need a module param is that this role gives you access to master.gnome.org, as such we need an existing maintainer to vouch for your access to be created given these permission allow you to modify tarballs we globally serve. The idea with this self-service tool is that we also introduced additional auditing and accounting when it comes to GNOME accounts, each action is tracked within an individual GitLab issue and we can easily connect what was granted and when. 3. If you do not have a GNOME Account at all, please use the new_account action, it'll make sure your account is created and access to GNOME's GitLab namespace is also granted. If you do have a GNOME account already and you need commit access please use the git_access action. Same applies if you're an existing maintainer and you need access to publish releases via master.gnome.org, in that case you will use the maint_access action. This will be the last update to this thread, for further updates please head to [1] or [2], thanks! [1] https://discourse.gnome.org/t/gnome-accounts-introducing-automation/11146/3 [2] https://wiki.gnome.org/Infrastructure/NewAccounts On Fri, Sep 16, 2022 at 11:32 AM Andrea Veri wrote: > Hello, > > As we discussed during GUADEC and as many of you know, processing new and > existing GNOME account changes has been a manual action for many years now. > With the introduction of OCP, GitLab CI/CD, IPA and SSO, we wanted to > enable GNOME contributors and developers to fulfil their needs in total > autonomy and freedom without requiring interventions from our side when it > came to provision resources or build/test GNOME software. > > With that in mind we're happy to announce new and existing GNOME account > changes are now processed via automation. > > How it works > --- > > When visiting [1] you will be shown an issue template composed of some > documentation on top and a json dictionary. The only field that requires an > update is the json dictionary, the following format should be used: > > action can be any of: > > 1. new_account > 2. git_access > 3. master_access > 4. update_email > > While the module key should be the name of any GNOME module as found > within [2], the module key should only be specified with the new_account, > git_access, master_access actions. > > The title of the issue should be: "Account request". > > Other key takes when selecting the new_account action: > > 1. Your name, surname and username will be computed out of your full name > as found in your GitLab profile > 2. The registered email on your account will be the one of your GitLab > profile > > Other key takes when selecting the update_email action: > > 1. The email that will be synchronized with IPA is the primary one you > have registered on your GitLab account, please make sure that one is > up-to-date > > What automation will take care of: > > 1. Generate your account information and allow the Accounts team to verify > compliance, also add necessary labels > 2. Mail individual existing GNOME module maintainers and have them > acknowledge your new or existing GNOME account request > 3. Once all the verifications have happened, automation will create your > account or update it with additional permissions > 4. Close the issue and turn the confidential flag to on once the full > process has completed > > Please let us know any feedback you may have, for any bug report please > use [3]. > > Once an initial phase of testing has happened, the idea we have is > introducing the same automation within the GNOME Foundation Membership > Committee as well during the coming months. > > Thanks! > > [1] > https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/new?issuable_template=account-request > [2] https://gitlab.gnome.org/GNOME > [3] https://gitlab.gnome.org/Infrastructure/Infrastructure/issues > > > -- > Cheers, > Andrea > > Principal Systems Engineer at Red Hat, > GNOME Infrastructure Team Coordinato
Retired IRC services: Commits Bot, MeetBot
Hi, with the advent of GitLab, Matrix and our desire to reduce the amount of services we maintain to lower maintenance burden I'm here to announce the following IRC services are being decommissioned: 1. Commits Bot (can be replaced with GitLab webhooks support and one of the available Matrix or IRC integrations) 2. MeetBot (last team using it dates back to 2019) Happy to help provide some help to anyone willing to migrate to webhooks and available integrations to supersede the solutions we've been running for a long time. Thanks! -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.dragonsreach.it ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Upcoming changes to GNOME's mail infrastructure
Hi, during early November the following changes will be applied to GNOME's mail infrastructure: 1. SPF records will be made more strict and outgoing email for any @ gnome.org e-mail will have to transit over GNOME's mail servers 2. DKIM will be introduced to sign emails originating from a @gnome.org alias 3. @gnome.org alias owners will have to change their mail client configuration to use GNOME mail servers as their SMTP server with authentication defaulting to their GNOME account credentials There will be another communication from our side with an exact list of modifications you will need to apply to comply with the above changes. As a friendly reminder all the mailing lists (with the exception of l10n lists which are undergoing a set of code changes on damned-lies) hosted on mail.gnome.org will be retired at the end of October 2022. Please see [1]. Thanks, [1] https://mail.gnome.org/archives/desktop-devel-list/2022-September/msg00018.html -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.dragonsreach.it ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Announcement: this mailing list will be retired by the end of Oct 2022
Hi, As we have been communicating during the past few months GNOME's Mailman platform is being decommissioned (python2 deprecation, major burden in managing lists spam). The deadline is currently set to the end of October 2022. Mailing list subscribers are invited to migrate to GNOME's Discourse instance [1]. Neil made sure [2] to create a set of tags you can re-use to initiate a new topic in the new platform, if a tag is missing please reach out to me directly. Jehan (from the GIMP Team) kindly provided some instructions you can follow [3] in order to safely migrate your reading workflow to Discourse. The new platform supports several login methods including your GNOME Account and other major OpenID providers. After the deadline of the end of October Mailman archives will remain alive in read only mode for posterity. If the mailing list was used behind an alias, please let me know so we can re-do the same setup but on Discourse instead. Thanks, P.S All the l10n lists are still pending code changes in damned-lies, the deadline to decommission those lists may slip by a week or two depending how soon those changes will be made available in DL codebase [1] https://discourse.gnome.org [2] https://mail.gnome.org/archives/desktop-devel-list/2022-September/msg00018.html [3] https://discourse.gnome.org/t/welcome-to-gimp-forum-on-gnome-discourse/11534/5 -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.dragonsreach.it ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Announcement: this mailing list will be retired by the end of Oct 2022
Hi, I’ve received several questions during the past days which possibly makes sense to summarize in a single topic [1] which I can then reference. Hopefully this specific post will help anyone looking for the same set of answers as well. If any additional common question arises I’ll make sure to add it to this same topic in Discourse. Thanks and please let us know if you have any questions around Discourse or your onboarding process! [1] https://discourse.gnome.org/t/common-questions-re-mailman-to-discourse/11841 On Thu, Oct 20, 2022 at 1:09 PM Andrea Veri wrote: > Hi, > > As we have been communicating during the past few months GNOME's Mailman > platform is being decommissioned (python2 deprecation, major burden in > managing lists spam). The deadline is currently set to the end of October > 2022. Mailing list subscribers are invited to migrate to GNOME's Discourse > instance [1]. Neil made sure [2] to create a set of tags you can re-use to > initiate a new topic in the new platform, if a tag is missing please reach > out to me directly. > > Jehan (from the GIMP Team) kindly provided some instructions you can > follow [3] in order to safely migrate your reading workflow to Discourse. > The new platform supports several login methods including your GNOME > Account and other major OpenID providers. > > After the deadline of the end of October Mailman archives will remain > alive in read only mode for posterity. If the mailing list was used behind > an alias, please let me know so we can re-do the same setup but on > Discourse instead. > > Thanks, > > P.S All the l10n lists are still pending code changes in damned-lies, the > deadline to decommission those lists may slip by a week or two depending > how soon those changes will be made available in DL codebase > > [1] https://discourse.gnome.org > [2] > https://mail.gnome.org/archives/desktop-devel-list/2022-September/msg00018.html > [3] > https://discourse.gnome.org/t/welcome-to-gimp-forum-on-gnome-discourse/11534/5 > > -- > Cheers, > Andrea > > Principal Systems Engineer at Red Hat, > GNOME Infrastructure Team Coordinator, > Former GNOME Foundation Board of Directors Secretary, > GNOME Foundation Membership & Elections Committee Chairman > > Homepage: https://www.dragonsreach.it > -- Cheers, Andrea Principal Systems Engineer at Red Hat, GNOME Infrastructure Team Coordinator, Former GNOME Foundation Board of Directors Secretary, GNOME Foundation Membership & Elections Committee Chairman Homepage: https://www.dragonsreach.it ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
