On Tue, Jan 27, 2009 at 1:10 PM, Rahul Sundaram
<sundaram@xxxxxxxxxxxxxxxxx> wrote:
> Chris Weyl wrote:
>
>> Of course we're here to meet users needs, but WE are those users as
>> well... and we're putting ourselves in a bad spot when we forget that.
>
> We are largely meeting needs other than ourselves though. Volunteer or not
> has nothing to do with it.
Really? If your management came to you and said that it's a condition
of employment that you fill out daily TPS reports in blood while
standing on your head, with the economy the way it is they could
probably do it. Try that with a volunteer.
>> I'm not sure what this "if you don't even want to try" bit is about,
>> since this isn't about me, it's about imposing another manual task on
>> our maintainers.
>
>> I do read the guidelines, and while there are MANY of them, they tend
>> to make sense, and where I don't think they do, I still respect them.
>
> No. Don't do that. If you don't think anything doesn't make sense, ask
> questions. We don't need to blindly respect anything.
I ... I'm not even going to respond to that.
>> I don't think you're "merely documenting them" here, however; this is
>> _clearly_ a new task being discussed.
>
> I don't think so. Bodhi description fields have been considered mandatory
> and filling them has always been a manual task. People just assumed,
> everyone would know what to fill it with. That hasn't worked out very well
> for us and has been a common question as well in #fedora-devel. By
> documenting them, we get that knowledge more easily preserved.
Really? Filling in that field has always been manual? hm. Funny this
works then:
bodhi -n -c "`cat clog`" -r F-X -t enhancement -R testing `make verrel`
-Chris
--
Chris Weyl
Ex astris, scientia
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
