What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
DID NOT REPORT
No report. Part of the "Projects in Trouble" e-mail to discuss future status.
The WSRP4J Project is an implementation of WSRP 1.0 Producer. WSRP is an OASIS specification that describes a protocol which allows portlets to be accessed remotely using Web Services. Incubating since: 2003 Not much news for WSRP4J - Apart from one committer working on refactoring the code base to match latest Pluto versions and one or two questions on the user mailing list, nothing really happened.
The WSRP4J Project is an implementation of WSRP 1.0 Producer. WSRP is an OASIS specification that describes a protocol which allows portlets to be accessed remotely using Web Services. Incubating since: 2003 The project is very silent, there are nearly no user questions and nearly zero developer activity. Although there seems to be a medium to high interest in wsrp over the past years, no community could be built around wsrp4j. There is still an open patent issue. The portals PMC is aware of these problems and will address them asap. ''iPMC Comments:'' * jukka: Good that someone is looking into this.
Nothing much happened in the project; the activity is very low - we voted in a new committer (Vishal Goenka) to get more active. WSRP4J is still in the move from the WS to the portals project (move of mailing lists is missing). We hope to get a more active community in the near future by incorporating the GSoC code.
WSRP4J has completed all graduation requirements except community participation. Things have been improving in this area recently. We added a new committer, Diego Louzan, in February. I have also met with various users from the higher education domain, and we have agreed that it would be beneficial for them to become more involved. We also have a Google Summer of Code student, Diego, who is working on two major areas: mavenizing and refactoring. The refactoring work will remove dependencies on Pluto as well as provide better separation of code among Producer, Consumer, and Common components.
* is the STATUS file up to date? (also post link) The cwiki file on the incubator site is up to date as well as the STATUS file in the project directory. http://incubator.apache.org/projects/wsrp4j.html * any legal, cross-project or personal issues that still need to be addressed? No. * what has been done for incubation since the last report? 1. Annointed a new committer: sgoldstein 2. Various bug fixes. 3. Restructured the website and added the Portals logo. 4. Migrated to the new moinmoin wiki. * plans and expectations for the next period? 1. Continue development work on outstanding WSRP 1.0 items (see TODO wiki: http://wiki.apache.org/portals/WSRP4JTodoList) 2. Continue to build the community by encouraging developers to contribute code. We are building a user population, but few outside developers have made code contributions. 3. Will probably ask for a vote to graduate from the Incubator into Portals. * any recommendations for how incubation could run more smoothly for you? None. * etc (your own thoughts on what is important would be helpful!)
* is the STATUS file up to date? (also post link) The cwiki file on the incubator site is up to date as well as the STATUS file in the project directory. http://incubator.apache.org/projects/wsrp4j.html * any legal, cross-project or personal issues that still need to be addressed? No. * what has been done for incubation since the last report? 1. Annointed a new committer: sgoldstein 2. Various bug fixes. 3. Restructured the website and added the Portals logo. 4. Migrated to the new moinmoin wiki. * plans and expectations for the next period? 1. Continue development work on outstanding WSRP 1.0 items (see TODO wiki: http://wiki.apache.org/portals/WSRP4JTodoList) 2. Continue to build the community by encouraging developers to contribute code. We are building a user population, but few outside developers have made code contributions. 3. Will probably ask for a vote to graduate from the Incubator into Portals. * any recommendations for how incubation could run more smoothly for you? None. * etc (your own thoughts on what is important would be helpful!)
