> On Sun, 17 Sep 2023, Florian Schmaus wrote:
>
>
>
> sounds perfectly fine.
Don't use an attribute if you can put the information in the (otherwise
empty) element. Especially, when other elements like already do it
that way.
> It would require (minor) adjustments to the schema and DT
On 9/17/23 20:28, Florian Schmaus wrote:
sounds perfectly fine.
Ideally I'd not limit it to only doi but also arxiv, zenodo, inspirehep.
They can all be referenced by https://... . I agree a specific type is
kind of unnecessary. However, the same paper can be referenced by all of
them.
On 17/09/2023 14.18, Alexander Neuwirth wrote:
Thanks. Instead of using the lang entry I can imagine these other
approaches:
2. Adding something specific to GLEP 68, like `type="doi"> https...`. However that seems like a bit too much work for
adding something that only a small subset of users
> On Sun, 17 Sep 2023, Alexander Neuwirth wrote:
> Thanks. Instead of using the lang entry I can imagine these other
> approaches:
> 1. doi/arxiv/... links could also easily be plugged in custom upstream
> remote ids, but that also feels a bit wrong since all other [upstream
> remote
> ids](h
Thanks. Instead of using the lang entry I can imagine these other
approaches:
1. doi/arxiv/... links could also easily be plugged in custom upstream
remote ids, but that also feels a bit wrong since all other [upstream
remote
ids](https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Upstrea
> On Fri, 15 Sep 2023, Alexander Neuwirth wrote:
> I am looking for a way to link scientific publications to
> ebuilds/packages. The easiest, but hacky way right now is to use the
> |https://doi.org/...|. Integration with
> |epkginfo|/|equery meta| works nicely out of the box. However,
> curr
Dear Larry,
I am looking for a way to link scientific publications to
ebuilds/packages. The easiest, but hacky way right now is to use the
|https://doi.org/...|. Integration with
|epkginfo|/|equery meta| works nicely out of the box. However, currently
|pkgcheck| and/or the XML format complain
On Wed, 16 Mar 2016 20:37:30 +0100
Dirkjan Ochtman wrote:
> On Wed, Mar 16, 2016 at 7:43 PM, Michał Górny wrote:
> > Therefore, I've been slowly writing a proper GLEP that would describe
> > all of metadata.xml in detail. Here's the current draft for review:
>
> Sounds like a good idea!
>
>
On Wed, 16 Mar 2016 20:37:30 +0100
Dirkjan Ochtman wrote:
> On Wed, Mar 16, 2016 at 7:43 PM, Michał Górny wrote:
> > Therefore, I've been slowly writing a proper GLEP that would describe
> > all of metadata.xml in detail. Here's the current draft for review:
>
> Sounds like a good idea!
>
>
Hello, all.
Long story short: while working on various metadata.xml-related
aspects, it bite us pretty hard that we lack proper spec for
metadata.xml file. What we have is pretty much the DTD, some partial
GLEPs (that sometimes provide incorrect info) and random bugs. ml
posts...
Therefore, I've
On Wed, Mar 16, 2016 at 7:43 PM, Michał Górny wrote:
> Therefore, I've been slowly writing a proper GLEP that would describe
> all of metadata.xml in detail. Here's the current draft for review:
Sounds like a good idea!
> https://wiki.gentoo.org/wiki/User:MGorny/GLEP:68
I reviewed your spec bas
On Fri, 18 Mar 2016 20:42:59 +0100
Johannes Huber wrote:
> Am Mittwoch 16 März 2016, 19:43:21 schrieb Michał Górny:
> > Hello, all.
> >
> > Long story short: while working on various metadata.xml-related
> > aspects, it bite us pretty hard that we lack proper spec for
> > metadata.xml file. What
Am Mittwoch 16 März 2016, 19:43:21 schrieb Michał Górny:
> Hello, all.
>
> Long story short: while working on various metadata.xml-related
> aspects, it bite us pretty hard that we lack proper spec for
> metadata.xml file. What we have is pretty much the DTD, some partial
> GLEPs (that sometimes p
Rich Freeman wrote:
> How about "contact" instead of team.
> there is no meaning to a contact besides being CC'ed on bugs.
Please simply call it cc then? :)
//Peter
On Tue, 9 Dec 2014 16:23:57 +0100
Jeroen Roovers wrote:
> On Tue, 9 Dec 2014 12:59:26 +0100
> Ulrich Mueller wrote:
>
> > > On Tue, 9 Dec 2014, Michał Górny wrote:
> >
> > > As for the exact details, I've pretty much decided to go for
> > > featurism here, IOW making everyone happy. It als
On 2014-12-10 10:41, Sergey Popov wrote:
> 09.12.2014 14:59, Ulrich Mueller пишет:
> > "proxy-maintainer" is very confusing because you won't put the proxy
> > maintainer there, but the user who is being proxied. Please rename
> > to something like "proxied" (assuming that this exists as a word in
On Tue, Dec 9, 2014 at 11:04 AM, Michał Górny wrote:
> Dnia 2014-12-09, o godz. 12:59:26
> Ulrich Mueller napisał(a):
>
>>
>> As the previously stated goal was to get rid of herds, I don't
>> understand why you want to reintroduce them as a value of the
>> type attribute. The existing herd elemen
On Wed, Dec 10, 2014 at 2:06 AM, Ulrich Mueller wrote:
>> On Tue, 9 Dec 2014, Rich Freeman wrote:
>
>> I thought we were generally agreed we wanted to get rid of herds.
>> The goal wasn't to rename them, but to get rid of them.
>
>> We could have email aliases for bugs so that people can sign
09.12.2014 14:59, Ulrich Mueller пишет:
> "proxy-maintainer" is very confusing because you won't put the proxy
> maintainer there, but the user who is being proxied. Please rename
> to something like "proxied" (assuming that this exists as a word in
> English) or "by-proxy".
+1 for that.
Proxy ma
Dnia 2014-12-09, o godz. 00:46:28
Michał Górny napisał(a):
> So considering the previous thread, the Council and QA discussions, I
> have prepared a new version of the metadata.xml update. To hopefully
> make everyone happy, I come with this three-step process:
And the Council meeting brought a
On 09/12/14 17:34, Michał Górny wrote:
I'm all for keeping it simple. However, backwards compatibility makes
it hard to keep things simple. I'd love to do, say, metadata.yml
supporting stuff like:
- maintainer: f...@gentoo.org, b...@gentoo.org
- maintainer:
- name: Foo Bar
email: f...@
> On Tue, 9 Dec 2014, Rich Freeman wrote:
> I thought we were generally agreed we wanted to get rid of herds.
> The goal wasn't to rename them, but to get rid of them.
> We could have email aliases for bugs so that people can sign up for
> notifications, but they would NOT be considered maint
Dnia 2014-12-09, o godz. 10:15:09
Michał Górny napisał(a):
> Dnia 2014-12-09, o godz. 00:46:28
> Michał Górny napisał(a):
>
> > Hello, all.
> >
> > So considering the previous thread, the Council and QA discussions, I
> > have prepared a new version of the metadata.xml update. To hopefully
> >
Dnia 2014-12-09, o godz. 18:59:22
Ulrich Mueller napisał(a):
> > On Tue, 9 Dec 2014, Michał Górny wrote:
>
> > That is *precisely the goal* of this. We scratch and
> > , and just use well-supported tag. type=""
> > is entirely optional, unobtrusive and backwards-compatible with
> > existin
> On Tue, 9 Dec 2014, Michał Górny wrote:
> That is *precisely the goal* of this. We scratch and
> , and just use well-supported tag. type=""
> is entirely optional, unobtrusive and backwards-compatible with
> existing apps. And yes, with just tag the rule in bug
> assignment is always to t
Dnia 2014-12-09, o godz. 17:17:35
"Andreas K. Huettel" napisał(a):
>
> > > As far as I know the typical way to edit metadata.xml files for all of us
> > > is still by hand in a text editor, and I prefer a lot typing
> > >
> > > kde
> > >
> > > over
> > >
> > > kde
> >
> >
> > k...@gentoo.
> > As far as I know the typical way to edit metadata.xml files for all of us
> > is still by hand in a text editor, and I prefer a lot typing
> >
> > kde
> >
> > over
> >
> > kde
>
>
> k...@gentoo.org
> Lovely KDE herd
>
>
> to be more precise.
Ugh. Even more ugly stuff from the depar
Dnia 2014-12-09, o godz. 12:59:26
Ulrich Mueller napisał(a):
> > On Tue, 9 Dec 2014, Michał Górny wrote:
>
> > As for the exact details, I've pretty much decided to go for
> > featurism here, IOW making everyone happy. It also proves how absurd
> > typing maintainers is but if you really fee
Dnia 2014-12-09, o godz. 16:49:24
"Andreas K. Huettel" napisał(a):
> Am Dienstag 09 Dezember 2014, 00:46:28 schrieb Michał Górny:
> > 2. Convert to ,
>
> Could any please explain to me why this additional
> xmlfication is of any ?
>
> As far as I know the typical way to edit metadata.xml fil
Am Dienstag 09 Dezember 2014, 00:46:28 schrieb Michał Górny:
> 2. Convert to ,
Could any please explain to me why this additional
xmlfication is of any ?
As far as I know the typical way to edit metadata.xml files for all of us is
still by hand in a text editor, and I prefer a lot typing
kde
On Tue, 9 Dec 2014 12:59:26 +0100
Ulrich Mueller wrote:
> > On Tue, 9 Dec 2014, Michał Górny wrote:
>
> > As for the exact details, I've pretty much decided to go for
> > featurism here, IOW making everyone happy. It also proves how absurd
> > typing maintainers is but if you really feel lik
> On Tue, 9 Dec 2014, Michał Górny wrote:
> As for the exact details, I've pretty much decided to go for
> featurism here, IOW making everyone happy. It also proves how absurd
> typing maintainers is but if you really feel like having it, sure.
> The default is 'developer', tags would be conv
Dnia 2014-12-09, o godz. 00:46:28
Michał Górny napisał(a):
> Hello, all.
>
> So considering the previous thread, the Council and QA discussions, I
> have prepared a new version of the metadata.xml update. To hopefully
> make everyone happy, I come with this three-step process:
>
> 1. Add type="
Hello, all.
So considering the previous thread, the Council and QA discussions, I
have prepared a new version of the metadata.xml update. To hopefully
make everyone happy, I come with this three-step process:
1. Add type="" attribute to tag (see attached patch),
2. Convert to ,
3. Eventually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-03-2010 06:39, Markos Chandras wrote:
> On Friday 26 February 2010 18:40:47 Alec Warner wrote:
>> You mistake the intent I think. We deploy automation because humans
>> fail; even when they have the best intentions. We make typos, copy
>> and p
On Friday 26 February 2010 18:40:47 Alec Warner wrote:
> On Thu, Feb 25, 2010 at 12:53 PM, Sebastian Pipping
wrote:
> > Stop.
> >
> > Is introduction of such a high level of bureaucracy really a good idea?
> >
> > In my eyes it could backfire and make matters worse as people either
> > - start
On Thu, Feb 25, 2010 at 12:53 PM, Sebastian Pipping wrote:
> Stop.
>
> Is introduction of such a high level of bureaucracy really a good idea?
>
> In my eyes it could backfire and make matters worse as people either
> - start ignoring it due to high noise
> - reduce people's activity below set per
Stop.
Is introduction of such a high level of bureaucracy really a good idea?
In my eyes it could backfire and make matters worse as people either
- start ignoring it due to high noise
- reduce people's activity below set permissions
To summarize presented proposal has a few points that may not
On 24-02-2010 23:41:26 +, Robin H. Johnson wrote:
> Proposed types:
> ---
> - version-bump
> - trivial-version-bump
> - trivial-fixes
> - fixes
> - enhancements
> - qa-fixes
> - trivial-qa-fixes
Isn't the QA team by its definition allowed to fix QA issues? If so, I
don't see a poi
On 02/25/2010 02:41 PM, Markos Chandras wrote:
On Thursday 25 February 2010 08:22:17 Ulrich Mueller wrote:
On Wed, 24 Feb 2010, Robin H Johnson wrote:
Metadata.xml should allow use of a element. Within
the element, package maintainers should be able to describe how
non-maintainer changes to th
> On Thu, 25 Feb 2010, Markos Chandras wrote:
>> Could we allow this element in the category metadata files, too?
>> Its value there would be the default for the category, with the
>> possibility to override it for individual packages.
> How are you so sure that a general "rule" can apply to
On Thursday 25 February 2010 08:22:17 Ulrich Mueller wrote:
> > On Wed, 24 Feb 2010, Robin H Johnson wrote:
> > Metadata.xml should allow use of a element. Within
> > the element, package maintainers should be able to describe how
> > non-maintainer changes to the package are handled.
>
> Cou
> On Wed, 24 Feb 2010, Robin H Johnson wrote:
> Metadata.xml should allow use of a element. Within
> the element, package maintainers should be able to describe how
> non-maintainer changes to the package are handled.
Could we allow this element in the category metadata files, too?
Its value
I'm forking this thread from -core, so we can have some useful
discussion about the idea, and then somebody can take it to the
gentoo-dev list.
This needs a lot more polishing still, and I'm not happy with some of
the semantics (esp. "policy" is too harsh a word for what we are trying
to convey).
On Mon, 28 Jul 2008 12:50:01 -0400
Doug Goldstein <[EMAIL PROTECTED]> wrote:
> If people wish to take specific categories, please let this thread
> know.
I'm working on net-analyzer.
Regards,
JeR
As a follow up to everyone. If you complete a category, please let it be
known in the correct place in use.local.desc.
We're at 37 of 131 categories complete, which pegs us at just over 28%
Doug Goldstein <[EMAIL PROTECTED]> wrote:
> If people wish to take specific categories, please let this thread
> know.
I just did the rox-base and rox-extra categories.
--
Jim Ramsay
Gentoo Developer (rox/fluxbox/gkrellm)
signature.asc
Description: PGP signature
Marius Mauch wrote:
On Mon, 28 Jul 2008 12:50:01 -0400
Doug Goldstein <[EMAIL PROTECTED]> wrote:
Please make sure you commit any changes to use.local.desc to
metadata.xml otherwise you risk the chance of having your changes
lost. I'm currently in the process of converting use.local.desc to
On Mon, 28 Jul 2008 12:50:01 -0400
Doug Goldstein <[EMAIL PROTECTED]> wrote:
> Please make sure you commit any changes to use.local.desc to
> metadata.xml otherwise you risk the chance of having your changes
> lost. I'm currently in the process of converting use.local.desc to
> metadata.xml. Aft
On 19:13 Mon 28 Jul , Ulrich Mueller wrote:
> > On Mon, 28 Jul 2008, Doug Goldstein wrote:
>
> > If people wish to take specific categories, please let this thread know.
>
> > Ford_Prefect is taking gnome-base
>
> I can take app-emacs and (the rest of) app-editors.
>
I take dev-scheme a
> On Mon, 28 Jul 2008, Doug Goldstein wrote:
> If people wish to take specific categories, please let this thread know.
> Ford_Prefect is taking gnome-base
I can take app-emacs and (the rest of) app-editors.
Ulrich
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug Goldstein wrote:
[...]
> Ford_Prefect is taking gnome-base
And gnome-extra.
Cheers,
Arun
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkiN/FIACgkQ+Vqt1inD4uyqkACghaEJjvUKUeNS1EFHUpoWih9M
fW8AoIsW8a174NLcHsF/TvwkSl
Please make sure you commit any changes to use.local.desc to
metadata.xml otherwise you risk the chance of having your changes lost.
I'm currently in the process of converting use.local.desc to
metadata.xml. After a category is converted, it will be auto-generated
EXCLUSIVELY from metadata.xml.
53 matches
Mail list logo
