public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ryszard Knop <ryszard.knop@linux.intel.com>
To: stephano <stephano.cetola@linux.intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] Groups.io Transition
Date: Tue, 02 Apr 2019 13:38:35 +0200	[thread overview]
Message-ID: <a80b8c1eb793433c331312b110584c1ce8831e22.camel@linux.intel.com> (raw)
In-Reply-To: <37a7ff05-3783-292b-4975-7bc572507f87@linux.intel.com>

Hi Stephano,
On https://edk2.groups.io/ the default group opened right away is
/g/devel, which is fine, but there isn't any indication of other groups
being available. It'd be useful to add links to other groups in the
description, for people not having your introductory mail linking other
groups available.
Thanks, Richard

On Thu, 2019-03-21 at 15:24 -0700, stephano wrote:
> First off, I'd like to thank Laszlo for his help in confirming the 
> functionality of the Groups.io mailing list. I could not have done
> this 
> without him. Groups.io seems to mimic our current list almost 100%, 
> certainly enough to make it viable. Also, it will allow such
> exciting 
> features as "email attachments", "email whitelisting", calendars,
> file 
> storage, and polls.
> 
> edk2-devel transition
> -------
> I am currently working with 01.org to archive our current mbox from 
> edk2-devel and move it over to Groups.io. Once this is complete we
> will 
> officially use that as our development mailing list.
> 
> 01.org and I are currently working out a date for the transition. I
> will 
> send out an email 2 weeks before the switch, again 1 week before the 
> switch, and 24 hours before we "go dark" on 01.org. Please update
> your 
> scripts / documents accordingly.
> 
> edk2-bugs transition
> -------
> Once we have been using groups.io for development emails for a few 
> weeks, I'll transition edk2-bugs over as well. I'd rather not do both
> at 
> the same time. Also, I want to give us a chance to collectively
> agree 
> that Groups.io is a successful platform.
> 
> Using Groups.io as a Community
> -------
> There are three "groups" in our current setup: devel, bugs, and 
> announce. Please take some time to familiarize yourself with the
> platform:
> 
> https://edk2.groups.io
> 
> The "default group" is devel, and that is where we will have any
> polls, 
> calendar updates, and file uploads. I will be sending out a Design 
> Meeting announcement soon which will rely heavily on this platform.
> 
> As always, please feel free to contact me with any questions or
> comments.
> 
> Cheers,
> Stephano
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel



  reply	other threads:[~2019-04-02 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 22:24 [edk2-announce] Groups.io Transition stephano
2019-04-02 11:38 ` Ryszard Knop [this message]
2019-04-02 12:55   ` stephano

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-list 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=a80b8c1eb793433c331312b110584c1ce8831e22.camel@linux.intel.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox