Hello everyone,
During last week's Collab summit, Jon Corbet suggested we use the power
of social media to improve the Linux kernel patch review process.
We thought this was a great idea, and have been experimenting with a new
Facebook group dedicated to patch discussion and review. The new group
provides a dramatically improved development workflow, including:
* One click patch or comment approval
* Comments enhanced with pictures and video
* Who has seen your patches and comments
* Searchable index of past submissions
* A strong community without anonymous flames
To help capture the group discussion in the final patch submission,
we suggest adding a Liked-by: tag to commits that have been through
group review.
To use the new group, please join:
https://www.facebook.com/groups/linuxpatches/
Once you've joined, you can post patches in the group, or email patches to
[email protected]
-chris
On 04/01/2014 05:41 PM, Chris Mason wrote:
>
> Hello everyone,
>
> During last week's Collab summit, Jon Corbet suggested we use the power
> of social media to improve the Linux kernel patch review process.
>
> We thought this was a great idea, and have been experimenting with a new
> Facebook group dedicated to patch discussion and review. The new group
> provides a dramatically improved development workflow, including:
>
> * One click patch or comment approval
> * Comments enhanced with pictures and video
> * Who has seen your patches and comments
> * Searchable index of past submissions
> * A strong community without anonymous flames
>
> To help capture the group discussion in the final patch submission,
> we suggest adding a Liked-by: tag to commits that have been through
> group review.
>
> To use the new group, please join:
>
> https://www.facebook.com/groups/linuxpatches/
>
> Once you've joined, you can post patches in the group, or email patches to
> [email protected]
>
> -chris
NACK! I do not have facebook and I do not like patches to be discussed
behind my back. On the mailing list we don't even want HTML with bold
lettered words so no thanks facebook adds nothing
Please obliterate this bad idea.
(And I do not have Facebook shares or care to)
yours truly
Boaz
On Tue, Apr 1, 2014 at 11:16 AM, Boaz Harrosh <[email protected]> wrote:
> On 04/01/2014 05:41 PM, Chris Mason wrote:
>>
>> Hello everyone,
>>
>> During last week's Collab summit, Jon Corbet suggested we use the power
>> of social media to improve the Linux kernel patch review process.
>>
>> We thought this was a great idea, and have been experimenting with a new
>> Facebook group dedicated to patch discussion and review. The new group
>> provides a dramatically improved development workflow, including:
>>
>> * One click patch or comment approval
>> * Comments enhanced with pictures and video
>> * Who has seen your patches and comments
>> * Searchable index of past submissions
>> * A strong community without anonymous flames
>>
>> To help capture the group discussion in the final patch submission,
>> we suggest adding a Liked-by: tag to commits that have been through
>> group review.
>>
>> To use the new group, please join:
>>
>> https://www.facebook.com/groups/linuxpatches/
>>
>> Once you've joined, you can post patches in the group, or email patches to
>> [email protected]
>>
>> -chris
>
> NACK! I do not have facebook and I do not like patches to be discussed
> behind my back. On the mailing list we don't even want HTML with bold
> lettered words so no thanks facebook adds nothing
>
> Please obliterate this bad idea.
So for those that don't use Facebook, we're also setting up a twitter
account that tweets patches 140 characters at a time. This should
help with review by automatically splitting up patches into manageable
140 character chunks.
josh
http://en.wikipedia.org/wiki/April_Fools%27_Day
On 04/01/2014 11:16 AM, Boaz Harrosh wrote:
> On 04/01/2014 05:41 PM, Chris Mason wrote:
>>
>> Hello everyone,
>>
>> During last week's Collab summit, Jon Corbet suggested we use the power
>> of social media to improve the Linux kernel patch review process.
>>
>> We thought this was a great idea, and have been experimenting with a new
>> Facebook group dedicated to patch discussion and review. The new group
>> provides a dramatically improved development workflow, including:
>>
>> * One click patch or comment approval
>> * Comments enhanced with pictures and video
>> * Who has seen your patches and comments
>> * Searchable index of past submissions
>> * A strong community without anonymous flames
>>
>> To help capture the group discussion in the final patch submission,
>> we suggest adding a Liked-by: tag to commits that have been through
>> group review.
>>
>> To use the new group, please join:
>>
>> https://www.facebook.com/groups/linuxpatches/
>>
>> Once you've joined, you can post patches in the group, or email patches to
>> [email protected]
>>
>> -chris
>
> NACK! I do not have facebook and I do not like patches to be discussed
> behind my back. On the mailing list we don't even want HTML with bold
> lettered words so no thanks facebook adds nothing
>
> Please obliterate this bad idea.
>
> (And I do not have Facebook shares or care to)
It's always hard to move on to new technologies. But at some point we
have to recognize that the internet has developed a rich culture that
the kernel community isn't taking full advantage of.
I certainly don't expect everyone to convert right away, but there's a
whole world out there beyond port 25.
-chris
On Tue, Apr 01, 2014 at 11:24:43AM -0400, Josh Boyer wrote:
>
> So for those that don't use Facebook, we're also setting up a twitter
> account that tweets patches 140 characters at a time. This should
> help with review by automatically splitting up patches into manageable
> 140 character chunks.
What a great way to up our commit count for the LWN statistics too!
Acked-by: Steven Rostedt <[email protected]>
-- Steve
On Tue, Apr 01, 2014 at 11:40:16AM -0400, Chris Mason wrote:
>
>
> On 04/01/2014 11:16 AM, Boaz Harrosh wrote:
> >On 04/01/2014 05:41 PM, Chris Mason wrote:
> >>
> >>Hello everyone,
> >>
> >>During last week's Collab summit, Jon Corbet suggested we use the power
> >>of social media to improve the Linux kernel patch review process.
> >>
> >>We thought this was a great idea, and have been experimenting with a new
> >>Facebook group dedicated to patch discussion and review. The new group
> >>provides a dramatically improved development workflow, including:
> >>
> >> * One click patch or comment approval
> >> * Comments enhanced with pictures and video
> >> * Who has seen your patches and comments
> >> * Searchable index of past submissions
> >> * A strong community without anonymous flames
> >>
> >>To help capture the group discussion in the final patch submission,
> >>we suggest adding a Liked-by: tag to commits that have been through
> >>group review.
> >>
> >>To use the new group, please join:
> >>
> >>https://www.facebook.com/groups/linuxpatches/
> >>
> >>Once you've joined, you can post patches in the group, or email patches to
> >>[email protected]
> >>
> >>-chris
> >
> >NACK! I do not have facebook and I do not like patches to be discussed
> >behind my back. On the mailing list we don't even want HTML with bold
> >lettered words so no thanks facebook adds nothing
> >
> >Please obliterate this bad idea.
> >
> >(And I do not have Facebook shares or care to)
>
> It's always hard to move on to new technologies. But at some point we have
> to recognize that the internet has developed a rich culture that the kernel
> community isn't taking full advantage of.
>
> I certainly don't expect everyone to convert right away, but there's a whole
> world out there beyond port 25.
Agreed
Acked-by: Felipe Balbi <[email protected]>
We might even be able to "recruit" a much more diverse group of
reviewers who are undiscovered as of now ;-)
--
balbi
Now that we have a Facebook group thanks to Chris Mason,
it's best to mention it in our Documentation so people
know where to go.
Signed-off-by: Felipe Balbi <[email protected]>
---
Documentation/SubmittingPatches | 39 +++++++++++++++++++++++++++------------
1 file changed, 27 insertions(+), 12 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 26b1e31..a3ce332 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -155,7 +155,22 @@ be able to justify all violations that remain in your patch.
-5) Select e-mail destination.
+5) Post your changes to our Facebook Group.
+
+We have a Facebook group at [1] where you *must* post your patches
+to prior to getting them accepted by any maintainer. In the near
+future, Facebook will become our only tool for patch reviewing
+since the Kernel community has decided to embrace Web 2.0.
+
+Make sure to join the group and start posting your patches there,
+instead of spamming everybody's inbox with countless patches each
+day.
+
+[1] https://www.facebook.com/groups/linuxpatches/
+
+
+
+6) Select e-mail destination.
Look through the MAINTAINERS file and the source code, and determine
if your change applies to a specific subsystem of the kernel, with
@@ -184,7 +199,7 @@ discussed should the patch then be submitted to Linus.
-6) Select your CC (e-mail carbon copy) list.
+7) Select your CC (e-mail carbon copy) list.
Unless you have a reason NOT to do so, CC [email protected].
@@ -225,7 +240,7 @@ Trivial patches must qualify for one of the following rules:
-7) No MIME, no links, no compression, no attachments. Just plain text.
+8) No MIME, no links, no compression, no attachments. Just plain text.
Linus and other kernel developers need to be able to read and comment
on the changes you are submitting. It is important for a kernel
@@ -248,7 +263,7 @@ you to re-send them using MIME.
See Documentation/email-clients.txt for hints about configuring
your e-mail client so that it sends your patches untouched.
-8) E-mail size.
+9) E-mail size.
When sending patches to Linus, always follow step #7.
@@ -259,7 +274,7 @@ server, and provide instead a URL (link) pointing to your patch.
-9) Name your kernel version.
+10) Name your kernel version.
It is important to note, either in the subject line or in the patch
description, the kernel version to which this patch applies.
@@ -269,7 +284,7 @@ Linus will not apply it.
-10) Don't get discouraged. Re-submit.
+11) Don't get discouraged. Re-submit.
After you have submitted your change, be patient and wait. If Linus
likes your change and applies it, it will appear in the next version
@@ -295,7 +310,7 @@ When in doubt, solicit comments on linux-kernel mailing list.
-11) Include PATCH in the subject
+12) Include PATCH in the subject
Due to high e-mail traffic to Linus, and to linux-kernel, it is common
convention to prefix your subject line with [PATCH]. This lets Linus
@@ -304,7 +319,7 @@ e-mail discussions.
-12) Sign your work
+13) Sign your work
To improve tracking of who did what, especially with patches that can
percolate to their final resting place in the kernel through several
@@ -399,7 +414,7 @@ tracking your trees, and to people trying to trouble-shoot bugs in your
tree.
-13) When to use Acked-by: and Cc:
+14) When to use Acked-by: and Cc:
The Signed-off-by: tag indicates that the signer was involved in the
development of the patch, or that he/she was in the patch's delivery path.
@@ -430,7 +445,7 @@ person it names. This tag documents that potentially interested parties
have been included in the discussion
-14) Using Reported-by:, Tested-by:, Reviewed-by: and Suggested-by:
+15) Using Reported-by:, Tested-by:, Reviewed-by: and Suggested-by:
If this patch fixes a problem reported by somebody else, consider adding a
Reported-by: tag to credit the reporter for their contribution. Please
@@ -486,7 +501,7 @@ idea reporters, they will, hopefully, be inspired to help us again in the
future.
-15) The canonical patch format
+16) The canonical patch format
The canonical patch subject line is:
@@ -600,7 +615,7 @@ See more details on the proper patch format in the following
references.
-16) Sending "git pull" requests (from Linus emails)
+17) Sending "git pull" requests (from Linus emails)
Please write the git repo address and branch name alone on the same line
so that I can't even by mistake pull from the wrong branch, and so
--
1.9.1.286.g5172cb3
On Tue, Apr 01, 2014 at 11:08:35AM -0500, Felipe Balbi wrote:
> Now that we have a Facebook group thanks to Chris Mason,
> it's best to mention it in our Documentation so people
> know where to go.
>
> Signed-off-by: Felipe Balbi <[email protected]>
Liked-by: Steven Rostedt <[email protected]>
-- Steve
Hi Felipe,
On Tue, Apr 01, 2014 at 11:08:35AM -0500, Felipe Balbi wrote:
> Now that we have a Facebook group thanks to Chris Mason,
> it's best to mention it in our Documentation so people
> know where to go.
>
> Signed-off-by: Felipe Balbi <[email protected]>
> ---
> Documentation/SubmittingPatches | 39 +++++++++++++++++++++++++++------------
> 1 file changed, 27 insertions(+), 12 deletions(-)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 26b1e31..a3ce332 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -155,7 +155,22 @@ be able to justify all violations that remain in your patch.
>
>
>
> -5) Select e-mail destination.
> +5) Post your changes to our Facebook Group.
> +
> +We have a Facebook group at [1] where you *must* post your patches
> +to prior to getting them accepted by any maintainer. In the near
> +future, Facebook will become our only tool for patch reviewing
> +since the Kernel community has decided to embrace Web 2.0.
> +
> +Make sure to join the group and start posting your patches there,
> +instead of spamming everybody's inbox with countless patches each
> +day.
> +
> +[1] https://www.facebook.com/groups/linuxpatches/
> +
> +
> +
> +6) Select e-mail destination.
No e-mail destination, please. Just flag a fb buddy account in the post
you're sending the patch. Maintainer will see on his/her timeline updates.
Br, David
>
> Look through the MAINTAINERS file and the source code, and determine
> if your change applies to a specific subsystem of the kernel, with
> @@ -184,7 +199,7 @@ discussed should the patch then be submitted to Linus.
>
>
>
> -6) Select your CC (e-mail carbon copy) list.
> +7) Select your CC (e-mail carbon copy) list.
>
> Unless you have a reason NOT to do so, CC [email protected].
>
> @@ -225,7 +240,7 @@ Trivial patches must qualify for one of the following rules:
>
>
>
> -7) No MIME, no links, no compression, no attachments. Just plain text.
> +8) No MIME, no links, no compression, no attachments. Just plain text.
>
> Linus and other kernel developers need to be able to read and comment
> on the changes you are submitting. It is important for a kernel
> @@ -248,7 +263,7 @@ you to re-send them using MIME.
> See Documentation/email-clients.txt for hints about configuring
> your e-mail client so that it sends your patches untouched.
>
> -8) E-mail size.
> +9) E-mail size.
>
> When sending patches to Linus, always follow step #7.
>
> @@ -259,7 +274,7 @@ server, and provide instead a URL (link) pointing to your patch.
>
>
>
> -9) Name your kernel version.
> +10) Name your kernel version.
>
> It is important to note, either in the subject line or in the patch
> description, the kernel version to which this patch applies.
> @@ -269,7 +284,7 @@ Linus will not apply it.
>
>
>
> -10) Don't get discouraged. Re-submit.
> +11) Don't get discouraged. Re-submit.
>
> After you have submitted your change, be patient and wait. If Linus
> likes your change and applies it, it will appear in the next version
> @@ -295,7 +310,7 @@ When in doubt, solicit comments on linux-kernel mailing list.
>
>
>
> -11) Include PATCH in the subject
> +12) Include PATCH in the subject
>
> Due to high e-mail traffic to Linus, and to linux-kernel, it is common
> convention to prefix your subject line with [PATCH]. This lets Linus
> @@ -304,7 +319,7 @@ e-mail discussions.
>
>
>
> -12) Sign your work
> +13) Sign your work
>
> To improve tracking of who did what, especially with patches that can
> percolate to their final resting place in the kernel through several
> @@ -399,7 +414,7 @@ tracking your trees, and to people trying to trouble-shoot bugs in your
> tree.
>
>
> -13) When to use Acked-by: and Cc:
> +14) When to use Acked-by: and Cc:
>
> The Signed-off-by: tag indicates that the signer was involved in the
> development of the patch, or that he/she was in the patch's delivery path.
> @@ -430,7 +445,7 @@ person it names. This tag documents that potentially interested parties
> have been included in the discussion
>
>
> -14) Using Reported-by:, Tested-by:, Reviewed-by: and Suggested-by:
> +15) Using Reported-by:, Tested-by:, Reviewed-by: and Suggested-by:
>
> If this patch fixes a problem reported by somebody else, consider adding a
> Reported-by: tag to credit the reporter for their contribution. Please
> @@ -486,7 +501,7 @@ idea reporters, they will, hopefully, be inspired to help us again in the
> future.
>
>
> -15) The canonical patch format
> +16) The canonical patch format
>
> The canonical patch subject line is:
>
> @@ -600,7 +615,7 @@ See more details on the proper patch format in the following
> references.
>
>
> -16) Sending "git pull" requests (from Linus emails)
> +17) Sending "git pull" requests (from Linus emails)
>
> Please write the git repo address and branch name alone on the same line
> so that I can't even by mistake pull from the wrong branch, and so
> --
> 1.9.1.286.g5172cb3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
One suggestion: the documentation should add a tip that if you can't
get someone to review your post, one option is to pay Facebook to
promote your post[1] so it shows more prominently (or at all) on more
kernel dvelopers' streams:
- Ted
[1] http://hothardware.com/News/Facebook-Looking-at-New-Revenue-Stream-Pay-To-Promote-Friends-Posts-/
On Wed, Apr 2, 2014 at 12:23 AM, Steven Rostedt <[email protected]> wrote:
> Liked-by: Steven Rostedt <[email protected]>
lovely Liked-by :-)
Liked-by: Jianyu Zhan <[email protected]>
Regards,
Jianyu Zhan
On 04/01/2014 04:32 PM, Theodore Ts'o wrote:
> One suggestion: the documentation should add a tip that if you can't
> get someone to review your post, one option is to pay Facebook to
> promote your post[1] so it shows more prominently (or at all) on more
> kernel dvelopers' streams:
A fine idea! I prefer the big newsfeed ads with video. I really want
to see the emotion behind your patch submission.
-chris
On Tue, 01.April.2014 17:55, Felipe Balbi wrote:
> On Tue, Apr 01, 2014 at 11:40:16AM -0400, Chris Mason wrote:
>>
>> On 04/01/2014 11:16 AM, Boaz Harrosh wrote:
>>> On 04/01/2014 05:41 PM, Chris Mason wrote:
>>>> Hello everyone,
>>>>
>>>> During last week's Collab summit, Jon Corbet suggested we use the power
>>>> of social media to improve the Linux kernel patch review process.
>>>>
>>>> We thought this was a great idea, and have been experimenting with a new
>>>> Facebook group dedicated to patch discussion and review. The new group
>>>> provides a dramatically improved development workflow, including:
>>>>
>>>> * One click patch or comment approval
>>>> * Comments enhanced with pictures and video
>>>> * Who has seen your patches and comments
>>>> * Searchable index of past submissions
>>>> * A strong community without anonymous flames
>>>>
>>>> To help capture the group discussion in the final patch submission,
>>>> we suggest adding a Liked-by: tag to commits that have been through
>>>> group review.
>>>>
>>>> To use the new group, please join:
>>>>
>>>> https://www.facebook.com/groups/linuxpatches/
>>>>
>>>> Once you've joined, you can post patches in the group, or email patches to
>>>> [email protected]
>>>>
>>>> -chris
>>> NACK! I do not have facebook and I do not like patches to be discussed
>>> behind my back. On the mailing list we don't even want HTML with bold
>>> lettered words so no thanks facebook adds nothing
>>>
>>> Please obliterate this bad idea.
>>>
>>> (And I do not have Facebook shares or care to)
>> It's always hard to move on to new technologies. But at some point we have
>> to recognize that the internet has developed a rich culture that the kernel
>> community isn't taking full advantage of.
>>
>> I certainly don't expect everyone to convert right away, but there's a whole
>> world out there beyond port 25.
> Agreed
>
> Acked-by: Felipe Balbi<[email protected]>
>
> We might even be able to "recruit" a much more diverse group of
> reviewers who are undiscovered as of now ;-)
>
Sorry, but definitely: Nack!!!
First of all, I do not think that it will truely support the whole
(business) process of code development and review.
Also, I do not think that it will attract more developers and reviewers.
But if you really think that your arguments are right, then why do not
use a solution that is based on the same social concepts like for
example Linux itself and set up an own social network or channel for the
whole Linux "eco-system" respectively community by using for example
Friendica [1], Diaspora [2], StatusNet [3], pump.io [4], or what else fits.
Have fun
Christian Stroetmannn
[1] Friendica http://www.friendica.com
[2] Diaspora diasporafoundation.org
[3] StatusNet http://www.status.net
[4] pump.io http://www.pump.io
On Tue, Apr 1, 2014 at 11:33 PM, Christian Stroetmann
<[email protected]> wrote:
> On Tue, 01.April.2014 17:55, Felipe Balbi wrote:
>>
>> On Tue, Apr 01, 2014 at 11:40:16AM -0400, Chris Mason wrote:
>>>
>>>
>>> On 04/01/2014 11:16 AM, Boaz Harrosh wrote:
>>>>
>>>> On 04/01/2014 05:41 PM, Chris Mason wrote:
>>>>>
>>>>> Hello everyone,
>>>>>
>>>>> During last week's Collab summit, Jon Corbet suggested we use the power
>>>>> of social media to improve the Linux kernel patch review process.
>>>>>
>>>>> We thought this was a great idea, and have been experimenting with a
>>>>> new
>>>>> Facebook group dedicated to patch discussion and review. The new group
>>>>> provides a dramatically improved development workflow, including:
>>>>>
>>>>> * One click patch or comment approval
>>>>> * Comments enhanced with pictures and video
>>>>> * Who has seen your patches and comments
>>>>> * Searchable index of past submissions
>>>>> * A strong community without anonymous flames
>>>>>
>>>>> To help capture the group discussion in the final patch submission,
>>>>> we suggest adding a Liked-by: tag to commits that have been through
>>>>> group review.
>>>>>
>>>>> To use the new group, please join:
>>>>>
>>>>> https://www.facebook.com/groups/linuxpatches/
>>>>>
>>>>> Once you've joined, you can post patches in the group, or email patches
>>>>> to
>>>>> [email protected]
>>>>>
>>>>> -chris
>>>>
>>>> NACK! I do not have facebook and I do not like patches to be discussed
>>>> behind my back. On the mailing list we don't even want HTML with bold
>>>> lettered words so no thanks facebook adds nothing
>>>>
>>>> Please obliterate this bad idea.
>>>>
>>>> (And I do not have Facebook shares or care to)
>>>
>>> It's always hard to move on to new technologies. But at some point we
>>> have
>>> to recognize that the internet has developed a rich culture that the
>>> kernel
>>> community isn't taking full advantage of.
>>>
>>> I certainly don't expect everyone to convert right away, but there's a
>>> whole
>>> world out there beyond port 25.
>>
>> Agreed
>>
>> Acked-by: Felipe Balbi<[email protected]>
>>
>> We might even be able to "recruit" a much more diverse group of
>> reviewers who are undiscovered as of now ;-)
>>
> Sorry, but definitely: Nack!!!
We (the majority of the Linux maintainers) voted already on fb.com to
make it out primary developing eco system
and will abandon LKML starting with April 1st.
--
Thanks,
//richard
Am 02.04.2014 00:02, schrieb Richard Weinberger:
> On Tue, Apr 1, 2014 at 11:33 PM, Christian Stroetmann
> <[email protected]> wrote:
>> On Tue, 01.April.2014 17:55, Felipe Balbi wrote:
>>> On Tue, Apr 01, 2014 at 11:40:16AM -0400, Chris Mason wrote:
>>>>
>>>> On 04/01/2014 11:16 AM, Boaz Harrosh wrote:
>>>>> On 04/01/2014 05:41 PM, Chris Mason wrote:
>>>>>> Hello everyone,
>>>>>>
>>>>>> During last week's Collab summit, Jon Corbet suggested we use the power
>>>>>> of social media to improve the Linux kernel patch review process.
>>>>>>
>>>>>> We thought this was a great idea, and have been experimenting with a
>>>>>> new
>>>>>> Facebook group dedicated to patch discussion and review. The new group
>>>>>> provides a dramatically improved development workflow, including:
>>>>>>
>>>>>> * One click patch or comment approval
>>>>>> * Comments enhanced with pictures and video
>>>>>> * Who has seen your patches and comments
>>>>>> * Searchable index of past submissions
>>>>>> * A strong community without anonymous flames
>>>>>>
>>>>>> To help capture the group discussion in the final patch submission,
>>>>>> we suggest adding a Liked-by: tag to commits that have been through
>>>>>> group review.
>>>>>>
>>>>>> To use the new group, please join:
>>>>>>
>>>>>> https://www.facebook.com/groups/linuxpatches/
>>>>>>
>>>>>> Once you've joined, you can post patches in the group, or email patches
>>>>>> to
>>>>>> [email protected]
>>>>>>
>>>>>> -chris
>>>>> NACK! I do not have facebook and I do not like patches to be discussed
>>>>> behind my back. On the mailing list we don't even want HTML with bold
>>>>> lettered words so no thanks facebook adds nothing
>>>>>
>>>>> Please obliterate this bad idea.
>>>>>
>>>>> (And I do not have Facebook shares or care to)
>>>> It's always hard to move on to new technologies. But at some point we
>>>> have
>>>> to recognize that the internet has developed a rich culture that the
>>>> kernel
>>>> community isn't taking full advantage of.
>>>>
>>>> I certainly don't expect everyone to convert right away, but there's a
>>>> whole
>>>> world out there beyond port 25.
>>> Agreed
>>>
>>> Acked-by: Felipe Balbi<[email protected]>
>>>
>>> We might even be able to "recruit" a much more diverse group of
>>> reviewers who are undiscovered as of now ;-)
>>>
>> Sorry, but definitely: Nack!!!
> We (the majority of the Linux maintainers) voted already on fb.com to
> make it out primary developing eco system
> and will abandon LKML starting with April 1st.
>
Please, allow me to ask some questions:
1. It was proposed "During last week's Collab summit" and now it is
decided already?
2. Do you have a link to the discussion on LKML or somewhere else?
3. Did you voted on fb.com or on LKML during?
4. Is there a link to the vote or any related informations?
5. You mean with "April 1st" since today respectively yesterday LKML
will be stopped to function?
6. And with "eco system" you mean that a majority of the Linux
maintainers want to use fb.com for the development of Linux?
Honestly, I do not find this funny somehow, but a little curious.
Best regards
C. Stroetmann
On Wed, Apr 02, 2014 at 12:20:31AM +0200, Christian Stroetmann wrote:
>
> Please, allow me to ask some questions:
> 1. It was proposed "During last week's Collab summit" and now it is
> decided already?
> 2. Do you have a link to the discussion on LKML or somewhere else?
> 3. Did you voted on fb.com or on LKML during?
> 4. Is there a link to the vote or any related informations?
> 5. You mean with "April 1st" since today respectively yesterday LKML
> will be stopped to function?
As it is no longer April 1st for you. We will have to start implementing it
come April 1st 2015.
-- Steve
> 6. And with "eco system" you mean that a majority of the Linux
> maintainers want to use fb.com for the development of Linux?
>
> Honestly, I do not find this funny somehow, but a little curious.
>
On Tue, Apr 01, 2014 at 04:32:08PM -0400, Theodore Ts'o wrote:
> One suggestion: the documentation should add a tip that if you can't
> get someone to review your post, one option is to pay Facebook to
> promote your post[1] so it shows more prominently (or at all) on more
> kernel dvelopers' streams:
>
> - Ted
>
> [1] http://hothardware.com/News/Facebook-Looking-at-New-Revenue-Stream-Pay-To-Promote-Friends-Posts-/
The more likes you get (or pay for), the more likely your patch will be
pulled into mainline.
-- Steve
Am 02.04.2014 00:20, schrieb Christian Stroetmann:
> Am 02.04.2014 00:02, schrieb Richard Weinberger:
>> On Tue, Apr 1, 2014 at 11:33 PM, Christian Stroetmann
>> <[email protected]> wrote:
>>> On Tue, 01.April.2014 17:55, Felipe Balbi wrote:
>>>> On Tue, Apr 01, 2014 at 11:40:16AM -0400, Chris Mason wrote:
>>>>>
>>>>> On 04/01/2014 11:16 AM, Boaz Harrosh wrote:
>>>>>> On 04/01/2014 05:41 PM, Chris Mason wrote:
>>>>>>> Hello everyone,
>>>>>>>
>>>>>>> During last week's Collab summit, Jon Corbet suggested we use
>>>>>>> the power
>>>>>>> of social media to improve the Linux kernel patch review process.
>>>>>>>
>>>>>>> We thought this was a great idea, and have been experimenting
>>>>>>> with a
>>>>>>> new
>>>>>>> Facebook group dedicated to patch discussion and review. The
>>>>>>> new group
>>>>>>> provides a dramatically improved development workflow, including:
>>>>>>>
>>>>>>> * One click patch or comment approval
>>>>>>> * Comments enhanced with pictures and video
>>>>>>> * Who has seen your patches and comments
>>>>>>> * Searchable index of past submissions
>>>>>>> * A strong community without anonymous flames
>>>>>>>
>>>>>>> To help capture the group discussion in the final patch submission,
>>>>>>> we suggest adding a Liked-by: tag to commits that have been through
>>>>>>> group review.
>>>>>>>
>>>>>>> To use the new group, please join:
>>>>>>>
>>>>>>> https://www.facebook.com/groups/linuxpatches/
>>>>>>>
>>>>>>> Once you've joined, you can post patches in the group, or email
>>>>>>> patches
>>>>>>> to
>>>>>>> [email protected]
>>>>>>>
>>>>>>> -chris
>>>>>> NACK! I do not have facebook and I do not like patches to be
>>>>>> discussed
>>>>>> behind my back. On the mailing list we don't even want HTML with
>>>>>> bold
>>>>>> lettered words so no thanks facebook adds nothing
>>>>>>
>>>>>> Please obliterate this bad idea.
>>>>>>
>>>>>> (And I do not have Facebook shares or care to)
>>>>> It's always hard to move on to new technologies. But at some point we
>>>>> have
>>>>> to recognize that the internet has developed a rich culture that the
>>>>> kernel
>>>>> community isn't taking full advantage of.
>>>>>
>>>>> I certainly don't expect everyone to convert right away, but
>>>>> there's a
>>>>> whole
>>>>> world out there beyond port 25.
>>>> Agreed
>>>>
>>>> Acked-by: Felipe Balbi<[email protected]>
>>>>
>>>> We might even be able to "recruit" a much more diverse group of
>>>> reviewers who are undiscovered as of now ;-)
>>>>
>>> Sorry, but definitely: Nack!!!
>> We (the majority of the Linux maintainers) voted already on fb.com to
>> make it out primary developing eco system
>> and will abandon LKML starting with April 1st.
>>
>
> Please, allow me to ask some questions:
> 1. It was proposed "During last week's Collab summit" and now it is
> decided already?
> 2. Do you have a link to the discussion on LKML or somewhere else?
> 3. Did you voted on fb.com or on LKML during?
> 4. Is there a link to the vote or any related informations?
> 5. You mean with "April 1st" since today respectively yesterday LKML
> will be stopped to function?
> 6. And with "eco system" you mean that a majority of the Linux
> maintainers want to use fb.com for the development of Linux?
>
> Honestly, I do not find this funny somehow, but a little curious.
>
>
>
> Best regards
> C. Stroetmann
>
If it was an April fool hoax, then I have to applaud Chris Mason and the
others a lot, get the post address for the beer, thank everybody for
telling me that there is a world besides the monitor, and beg your
pardon for my seriousness.
Now, it seems to be that I have to learn how to get my fb.com account
until April 2015. Hopefully, I can find a helping hand for this modern
technology.
Nevertheless, my suggestion to set such a platfrom up with an open
source framework was really meant in this way.
Good luck
Christian Stroetmann
On Tue, 2014-04-01 at 18:56 -0400, Steven Rostedt wrote:
> On Tue, Apr 01, 2014 at 04:32:08PM -0400, Theodore Ts'o wrote:
> > One suggestion: the documentation should add a tip that if you can't
> > get someone to review your post, one option is to pay Facebook to
> > promote your post[1] so it shows more prominently (or at all) on more
> > kernel dvelopers' streams:
> >
> > - Ted
> >
> > [1] http://hothardware.com/News/Facebook-Looking-at-New-Revenue-Stream-Pay-To-Promote-Friends-Posts-/
>
> The more likes you get (or pay for), the more likely your patch will be
> pulled into mainline.
I do not want to ruin your day guys, but I own a patent on this whole
idea.
Fortunately it ends in 20 years, April 1st, 2034, so you only have to be
patient.
On Tue, Apr 01, 2014 at 04:37:02PM -0700, Eric Dumazet wrote:
> On Tue, 2014-04-01 at 18:56 -0400, Steven Rostedt wrote:
> > On Tue, Apr 01, 2014 at 04:32:08PM -0400, Theodore Ts'o wrote:
> > > One suggestion: the documentation should add a tip that if you can't
> > > get someone to review your post, one option is to pay Facebook to
> > > promote your post[1] so it shows more prominently (or at all) on more
> > > kernel dvelopers' streams:
> > >
> > > - Ted
> > >
> > > [1] http://hothardware.com/News/Facebook-Looking-at-New-Revenue-Stream-Pay-To-Promote-Friends-Posts-/
> >
> > The more likes you get (or pay for), the more likely your patch will be
> > pulled into mainline.
>
>
> I do not want to ruin your day guys, but I own a patent on this whole
> idea.
>
> Fortunately it ends in 20 years, April 1st, 2034, so you only have to be
> patient.
Darn it... By then we will all become Government-controlled zombies with
brain implants. Looking at the bright side, though, we will be able to
review a patch by just thinking about it.
--
balbi
On Tue, 2014-04-01 at 16:37 -0700, Eric Dumazet wrote:
> I do not want to ruin your day guys, but I own a patent on this whole
> idea.
phfft.
Betcha your implementation-free idea patent won't hold up.
Prior art and such.
On 2014/4/1 22:41, Chris Mason wrote:
>
> Hello everyone,
>
> During last week's Collab summit, Jon Corbet suggested we use the power
> of social media to improve the Linux kernel patch review process.
>
> We thought this was a great idea, and have been experimenting with a new
> Facebook group dedicated to patch discussion and review. The new group
> provides a dramatically improved development workflow, including:
>
> * One click patch or comment approval
> * Comments enhanced with pictures and video
> * Who has seen your patches and comments
> * Searchable index of past submissions
> * A strong community without anonymous flames
>
> To help capture the group discussion in the final patch submission,
> we suggest adding a Liked-by: tag to commits that have been through
> group review.
>
> To use the new group, please join:
>
> https://www.facebook.com/groups/linuxpatches/
>
> Once you've joined, you can post patches in the group, or email patches to
> [email protected]
>
This is really a great idea! Unfortunately it's also a big block
to us Chinese developers, as we can't access http://www.facebook.com.
Any thing facebook can do? Like setup a http://www.facebook.cn and build
a blacklist so unwelcome messages won't show up in fb.cn.
On 04/01/2014 09:39 PM, Li Zefan wrote:
> On 2014/4/1 22:41, Chris Mason wrote:
>> Once you've joined, you can post patches in the group, or email patches to
>> [email protected]
>>
>
> This is really a great idea! Unfortunately it's also a big block
> to us Chinese developers, as we can't access http://www.facebook.com.
>
> Any thing facebook can do? Like setup a http://www.facebook.cn and build
> a blacklist so unwelcome messages won't show up in fb.cn.
I have to admit, this isn't an area I know much about. I'll ask around.
-chris