After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 648355 - Impossible to contribute any fixes to www.gnome.org content due to WordPress migration
Impossible to contribute any fixes to www.gnome.org content due to WordPress ...
Status: RESOLVED OBSOLETE
Product: website
Classification: Infrastructure
Component: www.gnome.org
current
Other Linux
: Urgent blocker
: ---
Assigned To: GNOME Web maintainers
GNOME Web maintainers
Depends on:
Blocks: 646091 647052
 
 
Reported: 2011-04-21 07:12 UTC by André Klapper
Modified: 2018-09-24 10:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description André Klapper 2011-04-21 07:12:15 UTC
From bug 647052 comment 3:

"The content of www.gnome.org is not stored on git. It uses WordPress tables 
in MySQL however. (we really should update GnomeWeb on wiki to explain those things)"

This is blocking any contributions to www.gnome.org.
And there's really enough open bugs.
Comment 1 André Klapper 2011-05-11 11:00:35 UTC
http://live.gnome.org/GnomeWeb/GnomeDotOrgAccounts ?
Comment 2 Andreas Nilsson 2011-06-09 17:31:55 UTC
So, as discussed on IRC, I think using Wordpress with accounts is way better than the old model, because the overlap between people who enjoy making website fixes, and people who love using git is really small :)

I'm happy to start handling out accounts (or rather continuing handling them out) as soon as we have a rough policy in place.
Started a discussion on this at gnome-web-list https://mail.gnome.org/archives/gnome-web-list/2011-June/msg00006.html
Comment 3 Olav Vitters 2011-06-09 18:05:13 UTC
Might be nice to hook up www.gnome.org to LDAP. So at least maintainers can automatically edit pages.
Comment 4 Andreas Nilsson 2011-06-09 18:15:24 UTC
Perhaps, vdepizzol found http://wordpress.org/extend/plugins/simple-ldap-login/
If we're fine with all maintainers having access to the website (they always did in the past) then I'm all right with this.
Comment 5 Andreas Nilsson 2011-06-09 19:41:12 UTC
After some discussion with Olav on IRC, I filed bug 652231 about LDAP support
Comment 6 Eduard Gotwig 2013-10-01 20:19:07 UTC
2 years later, this bug is still not fixed.


The website is outdated, and the translation template does not cover all strings of the website!

The application section is outdated, GNOME has new applications which do not get covered at all.
Comment 7 André Klapper 2013-10-02 08:28:32 UTC
(In reply to comment #6)
> The website is outdated, and the translation template does not cover all
> strings of the website!

Which ones are missing? Is there a specific bug report about that problem?

> The application section is outdated, GNOME has new applications which do not
> get covered at all.

Can you provide a link to the "application section" please?
Comment 8 Eduard Gotwig 2013-10-02 11:30:18 UTC
Here is my bug report for the i18n missing strings: https://bugzilla.gnome.org/show_bug.cgi?id=709254


and here for the applications section:

https://bugzilla.gnome.org/show_bug.cgi?id=709255
Comment 9 Magdalen Berns (irc magpie) 2014-01-16 22:27:57 UTC
Is it not possible to add wordpress sites to git? This seems odd. If the core application can exist on https://github.com/WordPress/WordPress then it seems like a development repository could be added to git.gnome.org if security reasons make it so access/visibility must be restricted for a master to be practical. I am not sure how easy that would be to implement in practice though.
Comment 10 Alexandre Franke 2014-01-17 15:16:34 UTC
(In reply to comment #9)
> Is it not possible to add wordpress sites to git? This seems odd. If the core
> application can exist on https://github.com/WordPress/WordPress then it seems
> like a development repository could be added to git.gnome.org if security
> reasons make it so access/visibility must be restricted for a master to be
> practical. I am not sure how easy that would be to implement in practice
> though.

This bug report is about being able to edit the website content, not about the code of the engine the website runs on.
Comment 11 Magdalen Berns (irc magpie) 2014-01-20 23:27:03 UTC
(In reply to comment #10)
> (In reply to comment #9)
> > Is it not possible to add wordpress sites to git? This seems odd. If the core
> > application can exist on https://github.com/WordPress/WordPress then it seems
> > like a development repository could be added to git.gnome.org if security
> > reasons make it so access/visibility must be restricted for a master to be
> > practical. I am not sure how easy that would be to implement in practice
> > though.
> 
> This bug report is about being able to edit the website content, not about the
> code of the engine the website runs on.

I am guided by the title of the bug:

Impossible to contribute any fixes to www.gnome.org thanks to WordPress migration
Comment 12 Alexandre Franke 2014-01-21 08:44:35 UTC
(In reply to comment #11)
> I am guided by the title of the bug:

I understand how this can be misleading. The fixes in question are fixes to the content, like typos, inaccuracies, or incompleteness. You can actually see it's the case by reading the first comments. Maybe we should rephrase the bug summary? Ideas welcome.
Comment 13 Magdalen Berns (irc magpie) 2014-01-21 20:35:36 UTC
Seems a good idea. 

Admittedly, as you pointed out, I am guilty of skim reading here but for searchability in bugzilla as well as skim readers :-) a more accurate heading would help.
Comment 14 GNOME Infrastructure Team 2018-09-24 10:17:37 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/Infrastructure/Websites/issues/54.