GNOME Bugzilla – Bug 779634
help: Clean up obsolete files
Last modified: 2017-04-08 12:39:08 UTC
help: Drop execute bit from help pages
Created attachment 347286 [details] [review] help: Drop execute bit from help pages
Created attachment 347287 [details] [review] help: Drop unused scrollkeeper files, svn changelog We already preserved the changelog in git
Created attachment 347288 [details] [review] Drop unused .cvsignore files
Thanks Jeremy, all three look good to me, I'll commit them sometime next week as I'm currently working on another project, which takes all of my free time. Just FYI, these days we use GitHub (https://github.com/tomboy-notes/tomboy) for both code and issue/feature tracking, so feel free to send PRs/submit bugs directly there.
Review of attachment 347288 [details] [review]: LGTM
(In reply to Alex Tereschenko from comment #4) > Just FYI, these days we use GitHub (https://github.com/tomboy-notes/tomboy) > for both code and issue/feature tracking, so feel free to send PRs/submit > bugs directly there. Do you want your project closed in bugzilla.gnome.org then? It's a bit unusual because usually it's GitHub that mirrors git.gnome.org not the other way around. Except for some projects that are GitHub only (like Flatpak or Appstream).
Yeah, it was decided a while ago that usign GH with its integrated issue/source code tracking is more convenient than separate services provided by GNOME. As for the Bugzilla - there's still quite a few items in the BZ, which I'm yet to go through to decide on closing/moving and closing per se would rather not be the best thing to do right now - that's why it's still active. But if we could just disable an ability to file new ones, with a message pointing to GH, that would be nice.
You can file a bug and see what the sysadmins say or ask in #sysadmin on irc.gnome.org. You might need to manually move all your bugs to Github first. I don't know. https://bugzilla.gnome.org/enter_bug.cgi?product=bugzilla.gnome.org&component=products%20and%20taxonomy
Committed with b9f3fc03ca68ab3f09612efae86650f4bbdd8774 815784f8b74b7b2042e6d1c27328aa2c9813ba27 304a86892f92ac082b49c60ae8e03144c601f624