So, I agree let's focus on revamping the widget catalog as a first step.
Let me know if you need any help with this.
As for the project organization, I'm not going to push hard to change this
if you're happy with it, I just wanted to point out the tradeoff that is
being made there. Basically we
Thanks for the input and the offer for help Edwin. I agree with most of
your ideas but I'm happy with the current state of our build and repo.
Mickael?
2. Revamp the widget catalog. This is the first thing prospective users of
Nebula will see, and it should convey accurate and useful
Hi,
Sorry my comments are a bit late (Easter holiday/Spring break).
From the consumer perspective, I agree that a table summarizing the
purpose, features and state of widgets is important. I think a table
with the following contents would be a good start:
- widget name
- one-liner
- This includes updating the documentation regularly, speaking at
conferences, writing blogs, adding more widgets
- Improve project management
Don't missunderstand me, you are doing a great job Wim, but the last
year there was fairly no action in Nebula. At least none that
Hi Hallvard,
Thanks for joining the discussion.
On Tue, Apr 9, 2013 at 8:42 PM, Hallvard Trætteberg h...@idi.ntnu.no wrote:
Hi,
Sorry my comments are a bit late (Easter holiday/Spring break).
From the consumer perspective, I agree that a table summarizing the
purpose, features and state
Hi,
sorry for the late reply, but here are my 2 cents. I have read all previous
answers, but I'm not sure if I remember everything. :)
I completely agree with your analysis Wim. What I think needs to be
improved is:
- we need to create a us ... a feeling that we all belong to a great
@Mickael
Incubation is actually a cool status, it makes things easier sometimes.
For Nebula, I also don't think there is a big benefit in turning it into a
released project. But there is no issue in being a release neither...
I see where you come from but I think EMO will disagree. Being a
@Edwin
Thank you for your positive feedback Edwin. That is highly appreciated.
Also, it is unclear what level of support can be expected of a particular
widget. I think we could be clearer about this. It would be great if we
could clearly identify on the web site a 'lead' for each widget.
@Patrick
It would also help, in that context, to maintain somewhere easily
visible the status of each of the components. It is helpful to potential
users to know whether it is alpha/beta/rc/production, as well as the level
of current attention it is getting from committers.
Yes, that is
Dear People,
After a good year of serving as co-lead of Nebula it is time to reflect
upon the status and future of the project. When I joined as co-lead there
were a number of things that I wanted to help with.
* make the project easier to consume
* fix the build and continuous release
* promote
My analysis for this is the following:
Widget authors are pretty much individualists. We have many widgets
and many authors but there is not sense of a one product like you
would have for other projects. Every widget is more or less self
sustained. Hence there is no us.
Most widgets are
Hi Wim,
First off, I'd like to say you've done a tremendous job in leading Nebula
and we all owe you a huge debt of gratitude for all you've done. I really
appreciate your analysis of the situation and fostering discussion of these
issues. Here is my view of the situation.
I look at Nebula as a
I agree with Edwin's suggestions to make Nebula simply an aggregator of
sub-projects.
It would also help, in that context, to maintain somewhere easily visible the
status of each of the components. It is helpful to potential users to know
whether it is alpha/beta/rc/production, as well as the
13 matches
Mail list logo
