Jenkins build is back to normal : isis-core-ubuntu #543
See https://builds.apache.org/job/isis-core-ubuntu/543/
Checking branding for Apache Isis TLP
As the current (and first) PMC chair for Apache Isis, I want to make sure that we are compliant with the ASF's branding requirements. Using [1] as my reference: * our site [2] has a TM on the header * our site has a short description on the home page, repeated on the download page [3] * our site has the required prominent link to main Apache pages on the header. * there is a DOAP file that has been registered (also referenced at [4]). With respect to the description, it suggests that it's best to pass the sample description by trademarks@ and/or legal-internal@, to ensure it's a proper trademark goods description. Accordingly, the description we have on our home page about Apache Isis says: *Apache Isis is a framework for rapidly developing domain-driven apps in Java. Write your business logic in entities, domain services and repositories, and the framework dynamically (at runtime) generates a representation of that domain model as a webapp or as a RESTful API. Use for prototyping or production.* From your perspective, is there anything that I've missed or should change in the above description? Thanks Dan Apache Isis PMC Chair [1] http://www.apache.org/foundation/marks/pmcs [2] http://isis.apache.org/ [3] http://isis.apache.org/download.html [4] http://isis.apache.org/support.html
Re: Checking branding for Apache Isis TLP
Looks fine to me. Best Regards Mike Burton On 3 Jan 2013, at 11:01, Dan Haywood d...@haywood-associates.co.uk wrote: As the current (and first) PMC chair for Apache Isis, I want to make sure that we are compliant with the ASF's branding requirements. Using [1] as my reference: * our site [2] has a TM on the header * our site has a short description on the home page, repeated on the download page [3] * our site has the required prominent link to main Apache pages on the header. * there is a DOAP file that has been registered (also referenced at [4]). With respect to the description, it suggests that it's best to pass the sample description by trademarks@ and/or legal-internal@, to ensure it's a proper trademark goods description. Accordingly, the description we have on our home page about Apache Isis says: *Apache Isis is a framework for rapidly developing domain-driven apps in Java. Write your business logic in entities, domain services and repositories, and the framework dynamically (at runtime) generates a representation of that domain model as a webapp or as a RESTful API. Use for prototyping or production.* From your perspective, is there anything that I've missed or should change in the above description? Thanks Dan Apache Isis PMC Chair [1] http://www.apache.org/foundation/marks/pmcs [2] http://isis.apache.org/ [3] http://isis.apache.org/download.html [4] http://isis.apache.org/support.html
[jira] [Created] (ISIS-292) Remove Authenticator#isValid method; should not be defined as part of API.
Dan Haywood created ISIS-292: Summary: Remove Authenticator#isValid method; should not be defined as part of API. Key: ISIS-292 URL: https://issues.apache.org/jira/browse/ISIS-292 Project: Isis Issue Type: New Feature Affects Versions: isis-1.0.0 Reporter: Dan Haywood Assignee: Dan Haywood Fix For: isis-2.0.0 This method is only ever called from a method within AuthenticatorAbstract. It is therefore not part of the API, but rather an implementation detail of AuthenticatorAbstract. As this is a breaking API change, required to be released in a major x.0.0 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ISIS-156) Renaming getName() and other methods in metamodel
[ https://issues.apache.org/jira/browse/ISIS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-156: - Fix Version/s: (was: isis-1.0.1) isis-2.0.0 Renaming getName() and other methods in metamodel - Key: ISIS-156 URL: https://issues.apache.org/jira/browse/ISIS-156 Project: Isis Issue Type: Improvement Components: Core Affects Versions: 0.1.2-incubating Reporter: Dan Haywood Assignee: Dan Haywood Priority: Trivial Fix For: isis-2.0.0 from email exchange on mailing list: Just completing change for spec names. To confirm that name == singular name, what we have at the moment is: getFullName - fully qualified class name getShortName - class name only getName - singular name with spacing getPluralName - the pluralised version with spacing It seems we have redundancy all along. Yup, that's what we have. Did mean to rename 'getName' to 'getSingularName', but I guess I forgot. I'll go ahead and do that. They are two types of name though which isn't obvious from the method names. The first two are actually identifiers and won't change, whereas the other two are dynamic and will change, especially on a localised client. We might want to reflect this with getFullIdentifier and getShortIdentifier. ; That's a good idea. I'll make that change too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (ISIS-293) Combine restful objects and wicket viewer into a single webapp
Dan Haywood created ISIS-293: Summary: Combine restful objects and wicket viewer into a single webapp Key: ISIS-293 URL: https://issues.apache.org/jira/browse/ISIS-293 Project: Isis Issue Type: Improvement Components: Archetypes Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ISIS-293) Combine restful objects and wicket viewer into a single webapp
[ https://issues.apache.org/jira/browse/ISIS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-293: - Affects Version/s: quickstart-wrj-archetype-1.0.0 Combine restful objects and wicket viewer into a single webapp -- Key: ISIS-293 URL: https://issues.apache.org/jira/browse/ISIS-293 Project: Isis Issue Type: Improvement Components: Archetypes Affects Versions: quickstart-wrj-archetype-1.0.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ISIS-293) Combine restful objects and wicket viewer into a single webapp
[ https://issues.apache.org/jira/browse/ISIS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-293: - Fix Version/s: quickstart-wrj-archetype-1.0.1 Combine restful objects and wicket viewer into a single webapp -- Key: ISIS-293 URL: https://issues.apache.org/jira/browse/ISIS-293 Project: Isis Issue Type: Improvement Components: Archetypes Affects Versions: quickstart-wrj-archetype-1.0.0 Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: quickstart-wrj-archetype-1.0.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (ISIS-294) Remove the old archetype (from 0.2.0) since is stale
Dan Haywood created ISIS-294: Summary: Remove the old archetype (from 0.2.0) since is stale Key: ISIS-294 URL: https://issues.apache.org/jira/browse/ISIS-294 Project: Isis Issue Type: Task Components: Archetypes Reporter: Dan Haywood Assignee: Dan Haywood Priority: Minor Fix For: GIT REPO only The example/archetype/quickstart archetype is out-of-date (from 0.2.0) and is liable to cause confusion. NB: the released example/archetype/quickstart_wicket_restful_jdo archetype should remain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
