I'm now adding it for OpenDBX and glorp. We should create lint rules for it ;)
On Thu, Dec 12, 2013 at 10:57 AM, Stéphane Ducasse < [email protected]> wrote: > Yes :) > In the output of the catalog itself > > > https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/? > > There is probably a typo in the generator catalogkeyClassesAndExample => > catalogKeyClassesAndExample > 1. Aconcagua > > Please define a class method named catalogDescription returning a > paragraph of description in the configuration class. > 1.1. Keywords > > Please define a class method named catalogKeywords returning an array of > symbols in the configuration class. > 1.2. Key classes and Implementations Notes > > Please define a class method named catalogkeyClassesAndExample returning > a paragraph describing the most important classes of the project and > relevant information such as an example. > 1.3. Key change logs > > Please define a class method named catalogChangeLog returning a paragraph > describing the most important changes in the configuration class. We > suggest to use the following format: > > - Version number - Date - topics > > > ConfigurationOfXXX project version: 'xx' ) load > > > or simply > > > - Version number - Date - topics > - Version number - Date - topics > - Version number - Date - topics > > > > On Dec 12, 2013, at 10:49 AM, Esteban Lorenzano <[email protected]> > wrote: > > is there a place where I can see the metadata methods I need to implement? > > Esteban > > > On Thu, Dec 12, 2013 at 9:59 AM, Stéphane Ducasse < > [email protected]> wrote: > >> Hi guys >> >> I really want to have an official catalog soon, so please add the missing >> metadata in your configurations. >> In addition I was discussing with robert pergl from Prague and he told me >> that >> when he has a problem with a package he does not know to whom he should >> report so >> I would like to add a catalogContact section. >> Any idea for improvement. >> >> Stef >> > > >
