[MEI-L] @clef* inside scoredef

[Johannes Kepper]

Hi all,

I would argue against using the sf.net tracker as open bugtracker. I think the TEI model seems better: Discuss things on TEI-L first. If there is consent that it is a bug, someone commits it to sf.net. So basically, discussion goes first. And the list definitely has a wider range than sf.net. I wouldn't recommend to automatically send a mail to MEI-L when there is activity on sf.net: Not everyone might want to get this level of detail… But generally speaking, I think this is someone that could be discussed during the virtual conference next week…

Best,
Johannes


Am 11.07.2011 um 11:33 schrieb Raffaele Viglianti:

> 
> 
> On Mon, Jul 11, 2011 at 10:16 AM, Peter Stadler <stadler at edirom.de> wrote:
> There *must* be a way to automatically send an email when a new ticket is created and the recipient could be MEI-L.
> I'd definitely opt for this approach rather than reporting bugs on the list (alone). Bug tracking is a great help for not forgetting bugs ;-)
> 
> 
> My thoughts exactly. An email notification would definitely attract my attention, for what it's worth.
> 
> Raffaele
>  
> Secondly, in terms of public image it's always good to create some activity on sourceforge...
> 
> All the best
> Peter
> 
> Am 11.07.2011 um 08:02 schrieb Andrew Hankinson, Mr:
> 
> > I think you'll get a better response from the list. Someone might see your message on the bug tracker a couple months from now, but I don't think anyone really looks at it on a daily basis.
> >
> > -Andrew
> >
> > On 2011-07-10, at 3:34 PM, TW wrote:
> >
> >> I'm wondering why the @clef* family of attributes is allowed on
> >> <scoredef>, but the <clef> element isn't.
> >>
> >> Is it O.K. to just drop a message to the list when I believe there are
> >> some inconsistencies in the specs?  I see that the tracker on
> >> Sourceforge hasn't been used yet, but I feel that would be a better
> >> place for posting such things.  Shall I take its virginity?
> >>
> >> Thomas Weber
> >>
> >> _______________________________________________
> >> mei-l mailing list
> >> mei-l at lists.uni-paderborn.de
> >> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> >
> >
> > _______________________________________________
> > mei-l mailing list
> > mei-l at lists.uni-paderborn.de
> > https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> 
> 
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> 
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l