[Gluster-users] [Gluster-devel] docs.gluster.org

[Amye Scavarda]

On Mon, Sep 4, 2017 at 1:28 AM, Niels de Vos <ndevos at redhat.com> wrote:
> On Fri, Sep 01, 2017 at 06:21:38PM -0400, Amye Scavarda wrote:
>> On Fri, Sep 1, 2017 at 9:42 AM, Michael Scherer <mscherer at redhat.com> wrote:
>> > Le vendredi 01 septembre 2017 à 14:02 +0100, Michael Scherer a écrit :
>> >> Le mercredi 30 août 2017 à 12:11 +0530, Nigel Babu a écrit :
>> >> > Hello,
>> >> >
>> >> > To reduce confusion, we've setup docs.gluster.org pointing to
>> >> > gluster.readthedocs.org. Both URLs will continue to work for the
>> >> > forseeable
>> >> > future.
>> >> >
>> >> > Please update any references that you control to point to
>> >> > docs.gluster.org. At
>> >> > some point in the distant future, we will switch to hosting
>> >> > docs.gluster.org on
>> >> > our own servers.
>> >> >
>> >> > RTD will set up a canonical link to docs.gluster.org[1]. Over time,
>> >> > this will
>> >> > change update the results on search engines to docs.gluster.org.
>> >> > This
>> >> > change
>> >> > will reduce confusion we've had with copies of our docs hosted on
>> >> > RTD.
>> >> >
>> >> > [1]: https://docs.readthedocs.io/en/latest/canonical.html
>> >>
>> >> So , seems TLS certificate is wrong, should we correct the link to be
>> >> http for now ?
>> >
>> > So I opened a few PR/review:
>> > https://github.com/gluster/glusterdocs/pull/259
>> >
>> > https://review.gluster.org/#/c/18182/
>> >
>> > https://github.com/gluster/glusterweb/pull/148
>> >
>> >
>> > --
>> > Michael Scherer
>> > Sysadmin, Community Infrastructure and Platform, OSAS
>> >
>> >
>> > _______________________________________________
>> > Gluster-devel mailing list
>> > Gluster-devel at gluster.org
>> > http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>> Fair warning, glusterweb is now deprecated as discussed in Community
>> Meeting on 30 Aug. However, github.com/gluster/glusterweb will be used
>> as a bug tracker moving forward.
>
> Could you please replace the contents of the current glusterweb
> repository with a README explaining this? The old files can stay in the
> history so that we can reference them in case something on the new
> website needs to be re-added.
>
> Being able to send pull requests and get contributions from users that
> way was one of the main reasons to move to GitHub. Is that still
> possible with the new site, in a different repository? I guess WordPress
> has some import/export features, but I don't know if those can get
> nicely combined with a repository on GitHub.
>
> Thanks!
> Niels

So we're actually going to move forward in a different direction with
the glusterweb repository once we get everything cleaned up.

We'll still use the GitHub issue queue as a method of tracking
improvements/bugs/feature requests , but I'd like to get us to a place
where we have a WordPress theme that people can contribute to and code
for custom plugins that we've developed. I'll be looking for
volunteers that can edit content directly as well.

I'll create a branch outlining what that could look like and we'll
discuss at the next community meeting.
- amye


-- 
Amye Scavarda | amye at redhat.com | Gluster Community Lead