Re: [Stlport-devel] Organisational stuff

[Petr O. <pt...@is...>]

On Friday 29 September 2006 00:15, Fran=E7ois Dumont wrote:
>=20
> I finally know how to configure STLport sourceforge project so that bugs=
=20
> report and patches are sent to mailing list.
>=20
> If no one mind I will do this configuration on sunday. Petr, it won't=20
> really impact you as you are also a member of the developers mailing=20
> list but you are for the moment the only one receiving patch reports so=20
> I would appreciate you give your opinion.

You will track messages from  Bugs/Support Requests/Patches/Feature Request=
s/Schedule
if you press 'Monitor' button (issue [#xxxx], top left, e.g.
https://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1562914&group=
_id=3D146814&atid=3D766244)

If you has assigned ticket, you will monitor it (if not reject monitoring).

But I'm strongly against put patches in mailing lists: only few people
sent patches in correct way via mail. Most sent it in unusable form.

=46rom my experience sending diffs via mail is inconvenient for tracking
problem and working with patches. You lost history (thanks IE for non-stand=
ard
mail headers for that), you lost state of issue, you lost issue owner...
But you take mail traffic with directly unusable diffs that you can't
associate with particular problem. Hmm. Fran=E7ois, you even not subscribed
to stlport-cvs to track changes in repo...

The issue tracking SF's system not best, but very good. It require some
study (as any non-trivial issue). But I don't expect this is a problem
for people who consider STLport as 'useful'.

>=20
> I only fear it will make mailing archives bigger but if we do a good job=
=20
> we will only have limited number of bug reports :-)

I'm doubt. I saw one issue tracking system with ability to work
via email, but it useful only for discussion and issue tracking
(patching is separate activity), and assume either restricted
access or good first-line support.

Resume: current bug/patch/etc. tracking is good enough. Just use it.

   - ptr


> Fran=E7ois Dumont wrote:
> >     One of the reason we move to sourceforge is that we (Petr and I) had
> > no access to this web site. I hope Boris Fomitchev will read you...
> > About the forum, the read-only status is only a note at the top of the
> > pages, you can still post messages if you want and there are still
> > people doing so :-( Redirecting people hitting the 'post' button on
> > stlport.org forums to the sourceforge ones would be great.
> >
> >     I am happy to see that I am not the only one that do not find some
> > of the sourceforge tools very intuitive :-) I am sure you can do what
> > you want and I would be very interested in doing the same, I just don't
> > know how.
> >
> > Dums
> >
> >
> > Ulrich Eckhardt wrote:
> >  =20
> >> I have two open issues that could use some work:
> >>
> >> - www.stlport.org
> >> This website still mentions 4.6.2 as the current release and is in gen=
eral far=20
> >> behind the reality. There is no mentioning of STLport5 at all, for exa=
mple.=20
> >> This is really a shame, because people will download 4.6.2, try to use=
 it and=20
> >> fail. If they don't give up, they might try the forum (which is read-o=
nly and=20
> >> redirects them to Sourceforge's), where they are probably first told t=
o=20
> >> download a recent 5.x release. We should put up a notice on the front =
of the=20
> >> stlport.org website.
> >>
> >> - Bug tracker notifications
> >> Is there a way to get notifications for bugs entered or changed? I don=
't have=20
> >> the time to regularly check existing entries for updates as it's prett=
y=20
> >> tiresome with a browser. I'd even forward this to the mailinglist here=
=2E BTW:=20
> >> this is also the reason why I personally prefer having patches sent he=
re, but=20
> >> maybe it's just that I don't know how to use Sourceforge properly.
> >>
> >> Uli