search

FreeUKGen / FreeUKGenealogy

Apache License 2.0
0 stars 0 forks source link

The website needs to be made manageable #6

Open archerbarrie opened 8 years ago

archerbarrie commented 8 years ago

The website needs to be organised so that it can be managed by any authorised person like the other production web sites.

PatReynolds commented 8 years ago

Executive Director, Technical Project Manager and Engagement Co-ordinator have Admin access and can edit blog, pages and structure (have password). ED and EC have a process to request, change, and check-and-go-live. Chair has user access (with password), but no permissions. Currently no-one can edit the 'help' section - this is advertised as a volunteer opportunity.

archerbarrie commented 5 years ago

So there is an unpublished process for managing the website. But why is it so undemocratic? Why can people not at least be notified when changes are made to the website? Why can not anyone propose a change? This is what happens, for example, in FreeBMD, and, I assume, the other websites as well, even without a CMS.

ghost commented 5 years ago

@archerbarrie Prior volunteer developer was not aware of the extant git repository for the site - we'll be using git going forward so feel free to add issues or contribute as you see fit.

Edit: Sorry for any confusion on my part - thought this was a new thread (I'll leave it to @PatReynolds to clarify).

Captainkirkdawson commented 5 years ago

Certainly does NOT happen with FR. We are totally issue driven with heavy emphasis on agile development. We work on a 2 week release cycle.

Kirk Dawson 5220 Riverside Drive Fairmont Hot Springs, B.C. V0B 1L1

On Thu, 22 Nov 2018 at 14:15, Barrie notifications@github.com wrote:

So there is an unpublished process for managing the website. But why is it so undemocratic? Why can people not at least be notified when changes are made to the website? Why can not anyone propose a change? This is what happens, for example, in FreeBMD, and, I assume, the other websites as well, even without a CMS.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeUKGenealogy/issues/6#issuecomment-441121052, or mute the thread https://github.com/notifications/unsubscribe-auth/ACvdRgKEdJCZSf9Le5l1dp_0JsxFjVGCks5uxxQFgaJpZM4IVJNY .

PatReynolds commented 5 years ago

There is a long recognised need for there to be changes needed at a fundamental level (over 18 momnths ago I secured an Amazon Web Services grant to allow one (the separate server) to happen, but this has been delayed for a number of reasons).

Anyone is free to propose a change to the website, or raise a bug. Most changes are as a result of consultation with users (e.g. blog>news) or arise from other projects (e.g. revision to onboarding of technical volunteers, which has come in part from Summers of Code, and in part from 'need to do better'. We have tended to use the Communication board rather than the his board for documenting and managing these issues, and I think that may need to continue in part, due to 'update the website' being a task that is part of a much greater whole. The communications board is worked in one-week sprints.

Access to both the Craft software, and the cms front end are both closely managed, with (for the front end) always a sign-off by a person who is not the person making the changes (who depends on the what - usually X asks Y to make a change, Y makes it, X reviews it, Y makes further changes, and X makes live or tells Y to make live.

monochromecyan commented 4 years ago

Perhaps there is a way to archive these tickets just to tidy up the board