On Apr 8, 2009, at 15:10, Tim wrote:
>
> I disagree. In fact, I've asked you (twice now) to send a statement of
> your own roles/responsibilities to the community for review and
> discussion. I still haven't seen it.
>
> I'm not saying that I think you are doing poorly -- from what I've
> seen,
> I think you are doing a great job -- but what Alan is doing is what I
> have asked you to do. (Two way street?)
Umm, I initiated that discussion with you, not the other way around,
remember? I have pasted the email in case you have forgotten.
---
March 2nd, 2009
Hi Tim,
Just wanted to drop you a quick not about the focus for the debmaster.
I realize this discussion might be better had on community forums, I
wanted to start it here in case all aspects of this discussion was not
ready for the community lists at the moment.
I see three technical areas, generally speaking, for the debmaster.
1. Creating packages for maemo
2. Maintaing tools for packaging and policy for packaging
3. Helping, along with the webmaster, to create healthy ecosystem of
repositories.
Obviously the debmaster ought to be hanging out in the community,
easily accessible to help with packaging and other related tasks, but
from that list above, what does the council feel should be a priority?
Recently, Niels suggested we use a tool called dak for the
repositories. This will take a lot of time, and I don't want the
community to feel I am not available. I am dividing my time to allow
for as much community contact as possible - in fact I do maemo stuff
on the weekends because I know developers are often active then. But I
would really like a clearer picture of where the pain is, at least
from the council's point of view. I have got a fairly clear picture
from the community.
Thanks,
Jeremiah
_______________________________________________
maemo-community mailing list
[email protected]
https://lists.maemo.org/mailman/listinfo/maemo-community
