Paweł Hajdan, Jr. | 14 Jun 2010 13:43
Picon
Favicon

removing "Gentoo Monthly Newsletter" links from the website

I think that the GMN (Gentoo Monthly Newsletter) is no longer "news",
and might give bad impression if it's exposed on the main page. We can
probably keep the contents for archival purposes.

I'm suggesting just to remove links to GMN from the main page. What do
you think?

Paweł

Petteri Räty | 14 Jun 2010 13:56
Picon
Favicon

Re: removing "Gentoo Monthly Newsletter" links from the website

On 14.6.2010 14.43, "Paweł Hajdan, Jr." wrote:
> I think that the GMN (Gentoo Monthly Newsletter) is no longer "news",
> and might give bad impression if it's exposed on the main page. We can
> probably keep the contents for archival purposes.
> 
> I'm suggesting just to remove links to GMN from the main page. What do
> you think?
> 
> Paweł
> 

Agreed.

Paweł Hajdan, Jr. | 14 Jun 2010 19:37
Picon
Favicon

removing dead projects

Here are some dead projects I've identified. I'm suggesting that we
remove them. What's active is active. Everything else is a distraction.

The number in parentheses is how long the project is inactive (approx).

http://www.gentoo.org/proj/en/desktop/research/ (6 years).
http://www.gentoo.org/proj/en/pr/gwn/ (3 years, and GWN is just dead).
http://www.gentoo.org/proj/en/pr/gmn/ (2 years, and GMN is also dead).
RepoSuperMan (a subproject of QA, nice idea, but likely dead).
http://www.gentoo.org/proj/en/releng/installer/ (1 year, but abandoned).
http://www.gentoo.org/proj/en/security/kernel.xml (2 years, dead).

What do you think?

Paweł

Alex Legler | 14 Jun 2010 20:05
Picon
Favicon

Re: removing dead projects

On Mon, 14 Jun 2010 19:37:31 +0200, "Paweł Hajdan, Jr."
<phajdan.jr <at> gentoo.org> wrote:

>http://www.gentoo.org/proj/en/security/kernel.xml (2
> years, dead).

Keep the page.

--

-- 
Alex Legler | Gentoo Security / Ruby
a3li <at> gentoo.org | a3li <at> jabber.ccc.de
Mike Frysinger | 14 Jun 2010 20:20
Picon
Favicon
Gravatar

Re: removing dead projects

On Mon, Jun 14, 2010 at 1:37 PM, "Paweł Hajdan, Jr." wrote:
> Here are some dead projects I've identified. I'm suggesting that we
> remove them. What's active is active. Everything else is a distraction.

what exactly do you mean by "remove them" ?  `cvs rm -f` in the cvs
tree ?  i dont think that's correct.  if a project is dead/orphaned,
then add a marker to the index.xml for it so it shows prominently when
people visit the page.
-mike

Paweł Hajdan, Jr. | 14 Jun 2010 21:43
Picon
Favicon

Re: removing dead projects

On 6/14/10 8:20 PM, Mike Frysinger wrote:
> what exactly do you mean by "remove them" ?  `cvs rm -f` in the cvs
> tree ?

Yeah, that's what I meant initially.

> i dont think that's correct.  if a project is dead/orphaned,
> then add a marker to the index.xml for it so it shows prominently when
> people visit the page.

Okay, could you give some more details about the marker?

> On 6/14/10 8:05 PM, Alex Legler wrote:
>> On Mon, 14 Jun 2010 19:37:31 +0200, "Paweł Hajdan, Jr."
>> <phajdan.jr <at> gentoo.org> wrote:
>>> http://www.gentoo.org/proj/en/security/kernel.xml (2
>>> years, dead).
>> Keep the page.

Okay. How about the marker that Mike suggested?

Paweł

Alec Warner | 16 Jun 2010 06:48
Picon
Favicon

Re: [gentoo-dev] The mis-concept of "slacking" in Gentoo

+project, -dev

On Tue, Jun 15, 2010 at 8:54 PM, Sebastian Pipping <sping <at> gentoo.org> wrote:
> Hello!
>
>
> When you are active in Gentoo during one week and less active during the
> next it may happen that people (sometimes jokingly) call you a
> "slacker".  This pattern seems to have become common enough that people
> even started calling themselves slackers when they are less active than
> potentially possible.  Is this reasonable and healthy?
>
> No, it isn't.
>

Why is it unhealthy?  Do you think it encourages people to 'always
meet their potential?'  I think it is very healthy for developers to
note when they cannot meet what many would consider their 'routine'
workload so that the community can attempt to detect and meeting these
staffing needs.  You may dislike the manner in which some developers
make this known 'hahaha I slacked off last week..' but the end result
is that it happens (often in .away messages.)

> As far as I know most if not all Gentoo developers do unpaid voluntary
> work in and for Gentoo.  So every single minute a Gentoo developer puts
> into Gentoo is a gift, incontrast to understanding every other minute a
> stolen one.  How come such a wrong concept even made it into the process
> of the council?  Officially being marked as a slacker?  Is that the only
> way to ensure an active council?

(Continue reading)

Paweł Hajdan, Jr. | 16 Jun 2010 18:46
Picon
Favicon

Re: [gentoo-dev] The mis-concept of "slacking" in Gentoo

On 6/16/10 5:54 AM, Sebastian Pipping wrote:
> As far as I know most if not all Gentoo developers do unpaid voluntary
> work in and for Gentoo.  So every single minute a Gentoo developer puts
> into Gentoo is a gift, incontrast to understanding every other minute a
> stolen one.  How come such a wrong concept even made it into the process
> of the council?  Officially being marked as a slacker?  Is that the only
> way to ensure an active council?

I think it's confusing you mention the council here. Council is there to
make decisions. If people miss the meetings, we can't make decisions.

Also, note that a council member can be proxied by other developer.

> To get this mis-concept out again I need your help.
> There is no such thing as slacking in Gentoo - no matter how many weeks
> you ran without commits.  It's time to get this understanding back to
> its healthy counterpart.

Could you explain more? Is it about people retiring because of that?

If so, then I agree we should permit some "leaves of absence" or maybe
even "sabbaticals" to keep talented people in the project, while
allowing them to rest.

Also, one can return after retiring.

Paweł

Steve Dibb | 16 Jun 2010 19:28
Picon
Favicon
Gravatar

Re: Re: [gentoo-dev] The mis-concept of "slacking" in Gentoo


>> To get this mis-concept out again I need your help.
>> There is no such thing as slacking in Gentoo - no matter how many weeks
>> you ran without commits.  It's time to get this understanding back to
>> its healthy counterpart.
>>      
>

I'm not sure what problem you are trying to tackle.

The way I see it, there are a few types of "slacker" status.

There are those who are just plain busy, and can't respond in a timely 
manner due to real-life issues.  Then there are a group who just don't 
have time for Gentoo as a regular maintenance task anymore, but still 
participate in discussions, development, etc.  Then there's the last 
group who are completely unresponsive and inactive -- these are the ones 
that are real blockers.

I don't like the idea of pretending there's no such thing as slacking, 
because there is.

We do have a practical problem (though I don't know how serious it is).  
We have healthy roll calls in some herds, but the developers are in a 
certain range of active to unresponsive.  When the herd is filled up, 
this gives developers and users the impression that it *should* be well 
tendered, but that may not be the case.

Steve

(Continue reading)

Jorge Manuel B. S. Vicetto | 17 Jun 2010 03:10
Picon
Favicon
Gravatar

Re: Re: [gentoo-dev] The mis-concept of "slacking" in Gentoo


On 16-06-2010 17:28, Steve Dibb wrote:
>>> To get this mis-concept out again I need your help.
>>> There is no such thing as slacking in Gentoo - no matter how many weeks
>>> you ran without commits.  It's time to get this understanding back to
>>> its healthy counterpart.
> 
> I'm not sure what problem you are trying to tackle.
> 
> The way I see it, there are a few types of "slacker" status.
> 
> There are those who are just plain busy, and can't respond in a timely
> manner due to real-life issues.  Then there are a group who just don't
> have time for Gentoo as a regular maintenance task anymore, but still
> participate in discussions, development, etc.  Then there's the last
> group who are completely unresponsive and inactive -- these are the ones
> that are real blockers.
> 
> I don't like the idea of pretending there's no such thing as slacking,
> because there is.
> 
> We do have a practical problem (though I don't know how serious it is). 
> We have healthy roll calls in some herds, but the developers are in a
> certain range of active to unresponsive.  When the herd is filled up,
> this gives developers and users the impression that it *should* be well
> tendered, but that may not be the case.

So everyone can have an idea, I'd suggest looking at the list of the
open retirement bugs[1].
As there seems to be some confusion about the policies to retire
(Continue reading)


Gmane