All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Pokorný <jpokorny@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Moving cluster project (Was: Moving gfs2-utils away from fedorahosted.org)
Date: Tue, 28 Feb 2017 03:18:03 +0100	[thread overview]
Message-ID: <20170228021803.GE10310@redhat.com> (raw)
In-Reply-To: <20170117212757.GB925@redhat.com>

On 17/01/17 22:27 +0100, Jan Pokorn? wrote:
> On 17/01/17 21:14 +0000, Andrew Price wrote:
>> On 17/01/17 19:58, Jan Pokorn? wrote:
>>> So I think we should arrange for a move to pagure.io for this cluster
>>> project as well if possible, if only to retain the ability to change
>>> something should there be a need.
>> 
>> Good plan.
>> 
>>> I can pursuit this if there are no complaints.  Just let me know
>>> (off-list) who aspires to cluster-maint group (to be created)
>>> membership.
>> 
>> Could you give the gfs2-utils-maint group push access to the cluster project
>> once it's been set up? (It is possible to add many groups to a project.) I
>> think that would be the most logical way to do it.
> 
> Sure and thanks for a cumulative access assignment tip.
> 
> I'll proceed on Friday or early next week, then.

Well, scheduler of mine didn't get to it until now, so sorry
to anyone starting to worry.

So what's been done:

- git repo moved over to https://pagure.io/linux-cluster/cluster
  + granted commit rights for gfs2-utils-maint group
    (and will add some more folks to linux-cluster group,
    feel free to bug me off-list about that)
  + mass-committed an explanation change to every branch at
    the discontinued fedorahosted.org (fh.o) provider I could,
    as some are already frozen
    (https://git.fedorahosted.org/cgit/cluster.git/)
  . I've decided to use a namespace (because there are possibly
    more projects to be migrated under that label), and have
    stuck with linux-cluster referring to the mailing list of
    the same name that once actively served to discuss the
    cluster stack in question (and is quite abandoned nowadays)

- quickly added backup location links at
  https://fedorahosted.org/cluster/ and
  https://fedorahosted.org/cluster/wiki/FenceAgentAPI, i.e.,
  the pages that seem most important to me, to allow for
  smooth "forward compatibility"; the links currently refer
  to vain stubs at ClusterLabs wiki, but that can be solved
  later on -- I am still unsure if trac wikis at fh.o will
  be served in the next phase or shut down right away and
  apparently this measure will help only in the former case

What to do:
- move releases over to pagure.io as well:
  https://fedorahosted.org/releases/c/l/cluster/
- possibly migrate some original wiki content to proper
  "doc pages" exposed directly through pagure.io
- resolve the question of the linked wiki stubs and
  cross-linking as such

Any comments?  Ideas?

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20170228/aeb83f1b/attachment.sig>

  reply	other threads:[~2017-02-28  2:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 16:48 [Cluster-devel] Moving projects away from fedorahosted.org Andrew Price
2017-01-16 18:45 ` [Cluster-devel] Moving gfs2-utils " Andrew Price
2017-01-17 19:58   ` Jan Pokorný
2017-01-17 21:14     ` Andrew Price
2017-01-17 21:27       ` [Cluster-devel] Moving cluster project (Was: Moving gfs2-utils away from fedorahosted.org) Jan Pokorný
2017-02-28  2:18         ` Jan Pokorný [this message]
2017-02-28 22:15           ` [Cluster-devel] Pagure.io as legacy codebases/distribution files/documentation hosting (Was: Moving cluster project) Jan Pokorný

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170228021803.GE10310@redhat.com \
    --to=jpokorny@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.