Documenting the mailing lists.

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

If we do this all at once, we can also ensure a consistent language, tone, etc.

I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

If we do this all at once, we can also ensure a consistent language, tone, etc.

I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

Regarding the text on the https://lists.yoctoproject.org link. Who maintains that page?

-----Original Message-----
From: Denys Dmytriyenko [mailto:[email protected]]
Sent: Monday, August 20, 2012 12:15 PM
To: Darren Hart
Cc: Yocto Project; Rifenbark, Scott M; Paul Gortmaker; Richard Purdie; Wold, Saul; Paul Eggleton; Osier-mixon, Jeffrey; Zanussi, Tom; Hudson, Sean; Koen Kooi; Jason Kridner; Flanagan, Elizabeth; Michael Halstead
Subject: Re: Documenting the mailing lists.

Quoted 11 lines · Darren Hart

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

Quoted 6 lines

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

I completely agree with this proposal to unify and clean up the mailing list references and descriptions. I didn't even know there was a separate page at
http://www.yoctoproject.org/community/mailing-lists - probably because I was happy with https://lists.yoctoproject.org/ all the time :)

Quoted 9 lines

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

Not sure if this improves much - in either case it's just a generic description of the mailing list that is specific to the corresponding layer, meta-ti. But I'm fine with the change, as long as we are unifying all the other list descriptions.

Quoted 2 lines

If we do this all at once, we can also ensure a consistent language, tone, etc.

Exactly! Thanks for initiating this.

Quoted 70 lines

I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

Signature · 1 line

Denys

I can replace the information on
http://www.yoctoproject.org/community/mailing-lists with a generic bit about mailing lists and then provide a link to the
https://lists.yoctoproject.org/ page.

Regarding the text on the
https://lists.yoctoproject.org link. Who maintains that page?

Scott

-----Original Message----- From: Denys Dmytriyenko [mailto:[email protected]] Sent: Monday, August 20, 2012 12:15 PM To:
Darren Hart Cc: Yocto Project; Rifenbark, Scott M; Paul Gortmaker; Richard Purdie; Wold, Saul; Paul Eggleton; Osier-mixon, Jeffrey; Zanussi, Tom; Hudson, Sean; Koen Kooi; Jason Kridner; Flanagan, Elizabeth; Michael Halstead Subject: Re: Documenting the mailing lists.

Quoted 12 lines · Darren Hart

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

Quoted 7 lines

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

I completely agree with this proposal to unify and clean up the mailing list references and descriptions. I didn't even know there was a separate page at
http://www.yoctoproject.org/community/mailing-lists - probably because I was happy with https://lists.yoctoproject.org/ all the time :)

Quoted 9 lines

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

Not sure if this improves much - in either case it's just a generic description of the mailing list that is specific to the corresponding layer, meta-ti. But I'm fine with the change, as long as we are unifying all the other list descriptions.

Quoted 2 lines

If we do this all at once, we can also ensure a consistent language, tone, etc.

Exactly! Thanks for initiating this.

Quoted 63 lines

I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current: ======== linux-yocto Development list for the
linux-yocto*.git Linux kernel repositories meta-ti Mailing list
for the meta-ti layer poky Poky build system developer discussion
& patch submission for meta-yocto shoeleather Neutral Board Lab
Mailing List yocto Discussion of all things Yocto yocto-ab Yocto
Project Advisory Board yocto-advocacy Yocto Project Advocacy &
Outreach AB Subgroup yocto-announce Announcements from the Yocto
Project yocto-bsp BSP Interest Group Yocto-builds Build failures
and discusion about the build system yocto-infrastructure Infrastructure

Proposed: ========= linux-yocto Development list for the
linux-yocto*.git Linux kernel repositories meta-ti Usage and
development list for the meta-ti layer poky Usage and development
list for the Poky build system (see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

I can replace the information on
http://www.yoctoproject.org/community/mailing-lists with a generic bit about mailing lists and then provide a link to the
https://lists.yoctoproject.org/ page.

Regarding the text on the
https://lists.yoctoproject.org link. Who maintains that page?

Scott

-----Original Message----- From: Denys Dmytriyenko [mailto:[email protected]] Sent: Monday, August 20, 2012 12:15 PM To:
Darren Hart Cc: Yocto Project; Rifenbark, Scott M; Paul Gortmaker; Richard Purdie; Wold, Saul; Paul Eggleton; Osier-mixon, Jeffrey; Zanussi, Tom; Hudson, Sean; Koen Kooi; Jason Kridner; Flanagan, Elizabeth; Michael Halstead Subject: Re: Documenting the mailing lists.

Quoted 12 lines · Darren Hart

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

Quoted 7 lines

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

I completely agree with this proposal to unify and clean up the mailing list references and descriptions. I didn't even know there was a separate page at
http://www.yoctoproject.org/community/mailing-lists - probably because I was happy with https://lists.yoctoproject.org/ all the time :)

Quoted 9 lines

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

Not sure if this improves much - in either case it's just a generic description of the mailing list that is specific to the corresponding layer, meta-ti. But I'm fine with the change, as long as we are unifying all the other list descriptions.

Quoted 2 lines

If we do this all at once, we can also ensure a consistent language, tone, etc.

Exactly! Thanks for initiating this.

Quoted 63 lines

I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current: ======== linux-yocto Development list for the
linux-yocto*.git Linux kernel repositories meta-ti Mailing list
for the meta-ti layer poky Poky build system developer discussion
& patch submission for meta-yocto shoeleather Neutral Board Lab
Mailing List yocto Discussion of all things Yocto yocto-ab Yocto
Project Advisory Board yocto-advocacy Yocto Project Advocacy &
Outreach AB Subgroup yocto-announce Announcements from the Yocto
Project yocto-bsp BSP Interest Group Yocto-builds Build failures
and discusion about the build system yocto-infrastructure Infrastructure

Proposed: ========= linux-yocto Development list for the
linux-yocto*.git Linux kernel repositories meta-ti Usage and
development list for the meta-ti layer poky Usage and development
list for the Poky build system (see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

If we do this all at once, we can also ensure a consistent language, tone, etc. I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

Quoted 91 lines · On Monday 20 August 2012 11:43:38 Darren Hart wrote:

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

If we do this all at once, we can also ensure a consistent language, tone, etc. I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

Quoted 8 lines

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

This is all good stuff, I'd just like to mention in case it is useful that I did update the list in the Reference Manual along with the information on how to contribute - which includes some direction on where to send patches. This is in the master version of the documentation but not the version currently shown on the website - we probably ought to fix that. We really ought to try to have all of this information consistent if at all possible.

Quoted 110 lines · Paul Eggleton

Quoted 100 lines · On Monday 20 August 2012 11:43:38 Darren Hart wrote:

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

If we do this all at once, we can also ensure a consistent language, tone, etc. I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel

repositories

meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch

submission for meta-yocto

shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel

repositories

meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system

(see README for patch submission)

shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:
Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and

development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

Quoted 8 lines

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

Quoted 7 lines

This is all good stuff, I'd just like to mention in case it is useful that I did update the list in the Reference Manual along with the information on how to contribute - which includes some direction on where to send patches. This is in the master version of the documentation but not the version currently shown on the website - we probably ought to fix that. We really ought to try to have all of this information consistent if at all possible.

Does it make sense to have this list in the reference manual? Should we perhaps just have it reference the README in the source (that way people can always see the current policy) and the long mailing list description? That reduces the redundancy to 2 from 4. Should be much easier to keep in sync.

Quoted 91 lines · On Monday 20 August 2012 11:43:38 Darren Hart wrote:

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

If we do this all at once, we can also ensure a consistent language, tone, etc. I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

Quoted 8 lines

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

This is all good stuff, I'd just like to mention in case it is useful that I did update the list in the Reference Manual along with the information on how to contribute - which includes some direction on where to send patches. This is in the master version of the documentation but not the version currently shown on the website - we probably ought to fix that. We really ought to try to have all of this information consistent if at all possible.

From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 2:28 PM

Does it make sense to have this list in the reference manual? Should we perhaps just have it reference the README in the source (that way people can always see the current policy) and the long mailing list description? That reduces the redundancy to 2 from 4. Should be much easier to keep in sync.

Here is what it says in the Reference Manual:

12.3. Mailing lists There are a number of mailing lists maintained by the Yocto Project as well as related OpenEmbedded mailing lists for discussion, patch submission and announcements. To subscribe to one of the following mailing lists, click on the appropriate URL in the following list and follow the instructions:
* http://lists.yoctoproject.org/listinfo/yocto - General Yocto Project discussion mailing list.
* http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core - Discussion mailing list about OpenEmbedded-Core (the core metadata).
* http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel - Discussion mailing list about OpenEmbedded.
* http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel - Discussion mailing list about the BitBake build tool.
* http://lists.yoctoproject.org/listinfo/poky - Discussion mailing list about Poky.
* http://lists.yoctoproject.org/listinfo/yocto-announce - Mailing list to receive official Yocto Project release and milestone announcements.

This is what Paul is referring to by way of corrections. I personally think it is useful to have something of a list in the Reference manual under this heading. I don't think we need the exact same wordings though in the Reference manual as would be found in https://lists.yoctoproject.org/. The stuff in the Reference manual should be general and give the reader an idea of the flavor of the lists. I can update the reference manual to include a link to https://lists.yoctoproject.org/ for the final say on each list.

Scott

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 2:28 PM
To: Paul Eggleton
Cc: Yocto Project; Rifenbark, Scott M; Paul Gortmaker; Richard Purdie; Wold, Saul; Osier-mixon, Jeffrey; Zanussi, Tom; Hudson, Sean; Denys Dmytriyenko; Koen Kooi; Jason Kridner; Flanagan, Elizabeth; Michael Halstead
Subject: Re: Documenting the mailing lists.

Quoted 101 lines · Paul Eggleton

Quoted 91 lines · On Monday 20 August 2012 11:43:38 Darren Hart wrote:

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

If we do this all at once, we can also ensure a consistent language, tone, etc. I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

Quoted 8 lines

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

Quoted 6 lines

This is all good stuff, I'd just like to mention in case it is useful that I did update the list in the Reference Manual along with the information on how to contribute - which includes some direction on where to send patches. This is in the master version of the documentation but not the version currently shown on the website - we probably ought to fix that. We really ought to try to have all of this information consistent if at all possible.

Does it make sense to have this list in the reference manual? Should we perhaps just have it reference the README in the source (that way people can always see the current policy) and the long mailing list description? That reduces the redundancy to 2 from 4. Should be much easier to keep in sync.

Here is what it says in the Reference Manual:

12.3. Mailing lists There are a number of mailing lists maintained by the Yocto Project as well as related OpenEmbedded mailing lists for discussion, patch submission and announcements. To subscribe to one of the following mailing lists, click on the appropriate URL in the following list and follow the instructions:
* http://lists.yoctoproject.org/listinfo/yocto - General Yocto Project discussion mailing list.
* http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core - Discussion mailing list about OpenEmbedded-Core (the core metadata).
* http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel - Discussion mailing list about OpenEmbedded.
* http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel - Discussion mailing list about the BitBake build tool.
* http://lists.yoctoproject.org/listinfo/poky - Discussion mailing list about Poky.
* http://lists.yoctoproject.org/listinfo/yocto-announce - Mailing list to receive official Yocto Project release and milestone announcements.

This is what Paul is referring to by way of corrections. I personally think it is useful to have something of a list in the Reference manual under this heading. I don't think we need the exact same wordings though in the Reference manual as would be found in https://lists.yoctoproject.org/. The stuff in the Reference manual should be general and give the reader an idea of the flavor of the lists. I can update the reference manual to include a link to https://lists.yoctoproject.org/ for the final say on each list.

Scott

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 2:28 PM
To: Paul Eggleton
Cc: Yocto Project; Rifenbark, Scott M; Paul Gortmaker; Richard Purdie; Wold, Saul; Osier-mixon, Jeffrey; Zanussi, Tom; Hudson, Sean; Denys Dmytriyenko; Koen Kooi; Jason Kridner; Flanagan, Elizabeth; Michael Halstead
Subject: Re: Documenting the mailing lists.

Quoted 101 lines · Paul Eggleton

Quoted 91 lines · On Monday 20 August 2012 11:43:38 Darren Hart wrote:

Scott,

We've come across some more confusion about mailing lists recently. I've sent a patch against poky to try and clear it up a bit in the source, but we should also see about cleaning up the web descriptions of the lists.

We have two pages that describe the lists:

http://www.yoctoproject.org/community/mailing-lists
https://lists.yoctoproject.org/

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

meta-ti Mailing list for the meta-ti layer

is not particularly enlightening. Perhaps something like:

meta-ti Usage and development of the meta-ti layer

If we do this all at once, we can also ensure a consistent language, tone, etc. I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Current:
========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Mailing list for the meta-ti layer
poky Poky build system developer discussion & patch
submission for meta-yocto
shoeleather Neutral Board Lab Mailing List
yocto Discussion of all things Yocto
yocto-ab Yocto Project Advisory Board
yocto-advocacy Yocto Project Advocacy & Outreach AB Subgroup
yocto-announce Announcements from the Yocto Project
yocto-bsp BSP Interest Group
Yocto-builds Build failures and discusion about the build system
yocto-infrastructure Infrastructure

Proposed:
=========
linux-yocto Development list for the linux-yocto*.git Linux kernel
repositories
meta-ti Usage and development list for the meta-ti layer
poky Usage and development list for the Poky build system
(see README for patch submission)
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

yocto General discussion list for the Yocto Project and
development for projects without dedicated lists

I think the yocto list is a bit problematic in that it mixes project conceptual discussion, user help desk, and development all on the same list. However, I'm trying to clarify what these actually are here - not change anything.

yocto-ab Yocto Project Advisory Board ???

This should imply the intended audience. Is it just meant for members? Is it meant as a way for non-AB members to observe what is going on?

yocto-advocacy Yocto Project advocacy & outreach AB subgroup

Same as above.

yocto-announce Announcements from the Yocto Project (low traffic)
yocto-bsp BSP Interest Group ???

There is no detailed description for this list, so I'm not sure what this is really about.

Yocto-builds Build failures and discussion about the autobuilder

(includes typo fix, "build system" removed to avoid confusion with the "poky build system")

Quoted 8 lines

yocto-infrastructure Infrastructure ???

Jefro or Michael, can you come up with something appropriate here?

For lists where certain guidelines should be used in communications and patch submission, we should document that in the detailed description of the list, such as [project] tags for example.

Quoted 6 lines

This is all good stuff, I'd just like to mention in case it is useful that I did update the list in the Reference Manual along with the information on how to contribute - which includes some direction on where to send patches. This is in the master version of the documentation but not the version currently shown on the website - we probably ought to fix that. We really ought to try to have all of this information consistent if at all possible.

Does it make sense to have this list in the reference manual? Should we perhaps just have it reference the README in the source (that way people can always see the current policy) and the long mailing list description? That reduces the redundancy to 2 from 4. Should be much easier to keep in sync.

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 1:44 PM
To: Yocto Project
Subject: Documenting the mailing lists.

My first recommendation would be to eliminate
http://www.yoctoproject.org/community/mailing-lists and replace links to it with links to https://lists.yoctoproject.org. This eliminates the need to keep the CMS version in sync with the mailman page. The mailman page should be considered the master anyway as the Description field is taken directly from the list administrative settings.

We should then work to create meaningful Descriptions of all the lists. These should still fit on a single line, but I think we can improve on what we have. For example:

If we do this all at once, we can also ensure a consistent language, tone, etc. I'll propose something for each list here and ask that interested parties comment and correct in reply. Once agreed upon, the admins of the respective lists can make the changes (all CC'd)

Proposed:
=========
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab

Quoted 5 lines

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 1:44 PM
To: Yocto Project
Subject: Documenting the mailing lists.

Proposed:
=========
shoeleather Neutral Board Lab Mailing List

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab
[Hudson, Sean] Sounds good to me.

Quoted 10 lines · Sean

Quoted 5 lines

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 1:44 PM
To: Yocto Project
Subject: Documenting the mailing lists.

Proposed:
=========
shoeleather Neutral Board Lab Mailing List

Quoted 6 lines

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab
[Hudson, Sean] Sounds good to me.

I've updated the description at https://lists.yoctoproject.org/

Quoted 11 lines · Michael Halstead

Quoted 10 lines · Sean

Quoted 5 lines

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 1:44 PM
To: Yocto Project
Subject: Documenting the mailing lists.

Proposed:
=========
shoeleather Neutral Board Lab Mailing List

Quoted 8 lines

Quoted 6 lines

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab
[Hudson, Sean] Sounds good to me.

I've updated the description at https://lists.yoctoproject.org/

Thanks Michael, let's hold off on any additional changes until we've been able to agree on the entire set, as we want to keep language, tense, etc. consistent. No need to change them multiple times.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

The mailing lists and website stuff is generally my responsibility, but please fix anything you like. :) Be aware that the new website is

under construction, so I am loathe to change much on the old website at this point. For the new one, it may be possible to dynamically grab the description from mailman.

Quoted 35 lines · Michael Halstead

Quoted 11 lines · Sean

Quoted 10 lines

Quoted 5 lines

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 1:44 PM
To: Yocto Project
Subject: Documenting the mailing lists.

Proposed:
=========
shoeleather Neutral Board Lab Mailing List

Quoted 8 lines

Quoted 6 lines

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab
[Hudson, Sean] Sounds good to me.

I've updated the description at https://lists.yoctoproject.org/

Thanks Michael, let's hold off on any additional changes until we've been able to agree on the entire set, as we want to keep language, tense, etc. consistent. No need to change them multiple times.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 2 lines · Jeff Osier-Mixon

The mailing lists and website stuff is generally my responsibility, but please fix anything you like. :) Be aware that the new website is

No intent to take over anything, I've just had to answer the "what goes where" question a few too many times these last couple of weeks and felt I should do something about it :-)

I made sure you were on CC so you could help guide this.

Quoted 3 lines

under construction, so I am loathe to change much on the old website at this point. For the new one, it may be possible to dynamically grab the description from mailman.

We'll still need descriptions of the non-yocto-project lists, so that may not be particularly helpful.

--
Darren

Quoted 29 lines · Darren Hart

Quoted 27 lines · Michael Halstead

Quoted 11 lines · Sean

Quoted 10 lines

Quoted 5 lines

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 1:44 PM
To: Yocto Project
Subject: Documenting the mailing lists.

Proposed:
=========
shoeleather Neutral Board Lab Mailing List

Quoted 8 lines

Quoted 6 lines

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab
[Hudson, Sean] Sounds good to me.

I've updated the description at https://lists.yoctoproject.org/

Thanks Michael, let's hold off on any additional changes until we've been able to agree on the entire set, as we want to keep language, tense, etc. consistent. No need to change them multiple times.

Quoted 11 lines

Quoted 8 lines

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel

Quoted 7 lines · Darren Hart

Quoted 2 lines · Jeff Osier-Mixon

The mailing lists and website stuff is generally my responsibility, but please fix anything you like. :) Be aware that the new website is

No intent to take over anything, I've just had to answer the "what goes where" question a few too many times these last couple of weeks and felt I should do something about it :-)

Oh, I'm not joking - please fix anything you want! or Scott or I can do it. Thanks for getting the ball rolling. I'll catch up on this thread.

Quoted 6 lines

I made sure you were on CC so you could help guide this.

Quoted 3 lines

under construction, so I am loathe to change much on the old website at this point. For the new one, it may be possible to dynamically grab the description from mailman.

Quoted 2 lines

We'll still need descriptions of the non-yocto-project lists, so that may not be particularly helpful.

The only YP-related, non-YP lists I currently track are openembedded-core and bitbake-devel. Both are OE lists, and I have recently volunteered to help admin, so can make sure they have valid Descriptions. If there are other lists we should track, please let me know and I'll add them to the pile.

Quoted 49 lines

--
Darren

Quoted 29 lines · Darren Hart

Quoted 27 lines · Michael Halstead

Quoted 11 lines · Sean

Quoted 10 lines

Quoted 5 lines

-----Original Message-----
From: Darren Hart [mailto:[email protected]]
Sent: Monday, August 20, 2012 1:44 PM
To: Yocto Project
Subject: Documenting the mailing lists.

Proposed:
=========
shoeleather Neutral Board Lab Mailing List

Quoted 8 lines

Quoted 6 lines

I'm not sure what "neutral" is meant to convey. How about:

Discussion list for the Shoeleather embedded board lab
[Hudson, Sean] Sounds good to me.

I've updated the description at https://lists.yoctoproject.org/

Thanks Michael, let's hold off on any additional changes until we've been able to agree on the entire set, as we want to keep language, tense, etc. consistent. No need to change them multiple times.

Quoted 11 lines

Quoted 8 lines

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel

Quoted 1 line · Jeff Osier-Mixon

On Mon, Aug 20, 2012 at 3:37 PM, Darren Hart <[email protected]>

Quoted 18 lines

Quoted 7 lines · Jeff Osier-Mixon

Quoted 2 lines

The mailing lists and website stuff is generally my responsibility, but please fix anything you like. :) Be aware that the new website is

No intent to take over anything, I've just had to answer the "what goes where" question a few too many times these last couple of weeks and felt I should do something about it :-)

Oh, I'm not joking - please fix anything you want! or Scott or I can do it. Thanks for getting the ball rolling. I'll catch up on this thread.

Quoted 6 lines

I made sure you were on CC so you could help guide this.

Quoted 3 lines

under construction, so I am loathe to change much on the old website at this point. For the new one, it may be possible to dynamically grab the description from mailman.

Quoted 8 lines

Quoted 2 lines

We'll still need descriptions of the non-yocto-project lists, so that may not be particularly helpful.

The only YP-related, non-YP lists I currently track are openembedded-core and bitbake-devel. Both are OE lists, and I have recently volunteered to help admin, so can make sure they have valid Descriptions. If there are other lists we should track, please let me know and I'll add them to the pile.

The only additional one that we reference in the manual is:

* http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
- Discussion mailing list about OpenEmbedded.

I'm not sure we need reference it at all though, perhaps oe-core is sufficient.

Quoted 2 lines · On Monday 20 August 2012 15:50:37 Darren Hart wrote:

Quoted 1 line · Jeff Osier-Mixon

On Mon, Aug 20, 2012 at 3:37 PM, Darren Hart <[email protected]>

Quoted 32 lines · wrote:

Quoted 18 lines

Quoted 7 lines · Jeff Osier-Mixon

Quoted 2 lines

The mailing lists and website stuff is generally my responsibility, but please fix anything you like. :) Be aware that the new website is

No intent to take over anything, I've just had to answer the "what goes where" question a few too many times these last couple of weeks and felt I should do something about it :-)

Oh, I'm not joking - please fix anything you want! or Scott or I can do it. Thanks for getting the ball rolling. I'll catch up on this thread.

Quoted 6 lines

I made sure you were on CC so you could help guide this.

Quoted 3 lines

under construction, so I am loathe to change much on the old website at this point. For the new one, it may be possible to dynamically grab the description from mailman.

Quoted 8 lines

Quoted 2 lines

We'll still need descriptions of the non-yocto-project lists, so that may not be particularly helpful.

The only YP-related, non-YP lists I currently track are openembedded-core and bitbake-devel. Both are OE lists, and I have recently volunteered to help admin, so can make sure they have valid Descriptions. If there are other lists we should track, please let me know and I'll add them to the pile.

The only additional one that we reference in the manual is:

* http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
- Discussion mailing list about OpenEmbedded.

Quoted 2 lines

I'm not sure we need reference it at all though, perhaps oe-core is sufficient.

FYI, the reason I added oe-devel is because it's the list that is used to discuss/submit patches for almost all OE community layers other than OE-Core and the ones that are hosted on yoctoproject.org.