The problem with this ridiculous diatribe is that there is no team
involvement! And furthermore (I'll put this in capital letters), ALEX DID
SEND THIS E-MAIL TO THE LIST TO SOLICIT FEEDBACK.
Yes, Bogdan, you've responded to a few defect issues over the last few days,
in a very cursory manor. So unless you - or any one else - is going to step
up to the plate, and actually participate, shut the hell up, and let anyone
willing to try do what they can. If you don't like it, spin off a static
version of Stellarium, and deal with that.
Now, I'll stop being an ass, and try to be a bit more constructive.
Alex is doing everything he can to make Stellarium better. He is asking for
input as much as he can. The lack of input & help is incredibly
frustrating. The app itself is already suffering, on at least to fronts:
OpenGL and plugin support. Not having the ability to address the OpenGL
issues myself prevents me from doing anything with that. I've pointed out
the deficiencies with the plugin system, and other than feedback that others
agree, I can get no consensus - or even ideas - on what should be done about
it.
Alex is in the same position as me regarding these two issues. That leaves
any defects that can be fixed, and adding things like better
internationalizations, etc. And as most users can't or don't want to
compile the app themselves, it's fully reasonable - and een responsible - to
put out releases on a regular basis. Which hasn't been happening in a very
long time, if ever at all.
The app is dying. This is unfortunate, but also the way of things. Fabian
& Mathew are no longer involved, and haven't been for well over a year.
That pretty much applies to you as well. This isn't a mater of blame;
everyone has a life, and no obligation for involvement. Without an OpenGL
expert, the defect count just continues to rise, and no one should really
believe that all of the issues are graphics card related. And without
developer involvement, the issues around plugins, and key bindings, is also
unlikely to be resolved.
So without strong, or even regular, developer involvement, people can only
do what they are capable of. That is what I did with the last release, and
Alex is doing now. Alex is also doing a better job at this relaese than I
did with 0.11.0; a much better job. If you want to help him, that's great.
I'm sure he'd much appreciate it, and I'm sure the release would be better
with your involvement.
Yes, some of the branching and commits have not gone correctly. Alex & I
have talked about this, and I think there is a better understanding.
I do not think anyone has an issue with involving the list, or even with
asking for your stamp of approval. But there has to be an expectation of a
reasonable time period.
On Wed, Oct 12, 2011 at 10:12 AM, Bogdan Marinov <[email protected]>wrote:
> On Mon, Oct 10, 2011 at 11:51 AM, Alexander Wolf <[email protected]>
> wrote:
> > Greetings all!
> >
> > This needs to go out as soon as possible - we add the new skyculture and
> > update translations. Plus we have fixed over 10 bugs. The progress of
> > development has very slowly and we have some unsolved bugs with hight
> > priority level. I'm going to create a all version over this weekend.
>
> Oh, my, another "renegade" release. Try not to make it a habit. Let me
> put it in capital letters:
>
> AFTER DECIDING SOMETHING ON THE IRC CHANNEL, SEND A LETTER TO THE
> MAILING LIST FOR THE PEOPLE WHO HAVEN'T PARTICIPATED IN THE
> DISCUSSION.
>
> People shouldn't be learning of a new release when this appears in a
> Google search:
> https://launchpad.net/stellarium/+announcement/9004
>
> (Sideline: before, notifying the translators happened by posting to
> the Translators forum and to the mailing list of the Stellarium
> Translators team in Launchpad. That team no longer appears to be
> connected to Stellarium's translations. Who changed it last? Is it in
> use in any way at all?)
>
> I understand that there's a separate branch:
> https://code.launchpad.net/~stellarium/stellarium/0.11
> But there is some misunderstanding how it should be used:
> https://bugs.launchpad.net/stellarium/+bug/871313
>
> The last release also had branch problems. I think that there are at
> least two revisions tagged as "0.11.0" and none of them matches the
> code actually released.
>
> Looking at what has actually been committed, there stuff like this:
> http://bazaar.launchpad.net/~stellarium/stellarium/0.11/revision/4921
> which shouldn't have been done without discussion with the rest of the
> team. (Locations is a mess, yes. Let's not make them messier.)
>
> Bogdan
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Stellarium-pubdevel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Stellarium-pubdevel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
