Re: Images in source code.

[Felix Meschberger]

Here: http://www.sno.phy.queensu.ca/~phil/exiftool/ ?

and http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html

(Thanks Google ;-) )

Regards
Felix

Am 15.06.2017 um 16:46 schrieb Martin Gainty 
>:

James and Team


quick update I have factored rat-plugin to read XMP (an XML metadata-tagged 
file with embedded Image)

i have tried adding metadata tags using the crippled freebie photoshop and 
could not find any way to add metadata tags to PNG, JPG or PSD as the 
File/FileInfo menu in freebie photoshop is hopelessly greyed out/disabled

Im reading some blogs that exiftool can add metadata tags to any existing 
image

Any clues as to where to locate any tool that can add metadata tag to an Image 
would be appreciated


Thanks,

Martin
__




From: Martin Gainty >
Sent: Sunday, June 4, 2017 8:49 AM
To: general@incubator.apache.org
Subject: Re: Images in source code.


is there anyway to run maven-rat-plugin to make sure ASF licensed assets are 
*not* being subverted by salesforce


http://creadur.apache.org/rat/apache-rat-plugin/rat-mojo.html


Apache Rat™ Plugin for Apache Maven – 
apache-rat:rat
creadur.apache.org
apache-rat:rat. Note:This goal should be used as a Maven report. Full name: 
org.apache.rat:apache-rat-plugin:0.13-SNAPSHOT:rat. Description:

?

Martin
__




From: John D. Ament 
Sent: Saturday, June 3, 2017 9:46 AM
To: general@incubator.apache.org
Subject: Re: Images in source code.

On Fri, Jun 2, 2017 at 8:20 PM Craig Russell  wrote:

Hi James,

Everything that is not explicitly called out in the top level NOTICE and
LICENSE files are licensed under the Apache 2.0 license.

Adding a file to this directory might mislead people into thinking that
they need to perform more due diligence with other files in other
directories.

My advice is to *not* add anything. Let the images be licensed per the
terms the top level LICENSE file.


Agreed.  What we do like to make sure is called out is if there is
provenance that these images came from somewhere else.  If these images
were not created by you and were not already under apache license, then we
would have a concern.



Craig

On Jun 2, 2017, at 2:20 PM, James Bognar 
wrote:

Thanks!

I haven't found a metadata editor that works yet, so I'll just add a
LICENSE.txt file to the directory.  Hopefully that's enough.

On Fri, Jun 2, 2017 at 4:48 PM, Josh Elser  wrote:

On 6/2/17 1:15 PM, James Bognar wrote:

I just added several png files to the source tree of our podling.  I
created them myself.  Are there any best-practices on how to mark
these as
Apache licensed?


I'm not sure of a good way to track this. I'm not sure if png supports
arbitrary metadata which could be edited. Some ways I've seen used
elsewhere to try to better propagate license/ownership:

* Comments on the issue-tracker issue that introduced them citing
origin/source (typically for images that are copied, not created)
* Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of course)
* A README in the same directory with relevant info

If the images are of the podling's creation, I wouldn't be particularly
worried. The copyright notice on your source-release and LICENSE are
sufficient to inform downstream consumers.

Probably not the answer you're looking for, but hope it helps :)

- Josh

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




--
James Bognar

Craig L Russell
c...@apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Migration of Podling Maintenance Tooling to Whimsy

[Felix Meschberger]

+1

Particularly as these are not day-to-day but every-now-and-then tasks ..

Regards
Felix

> Am 05.06.2017 um 17:32 schrieb Julian Hyde :
> 
> +1
> 
> It moves us towards a self-service (dare I say “github-like”) experience for 
> podlings, and that is always good.
> 
> Furthermore, if there are choices to be made (e.g. svnpubsub vs. CMS) I think 
> the tooling should strongly encourage them to take the “standard” option. 
> Maybe it doesn’t even present the other option(s) at all. When my project was 
> going through incubation I was forever worried about stepping on some 
> infrastructure landmine and as a result did nothing for several months.
> 
> Julian
> 
> 
>> On Jun 4, 2017, at 7:33 PM, John D. Ament  wrote:
>> 
>> All,
>> 
>> I want to bring up this discussion to see others opinions.  I would like to
>> move forward on migrating podling status maintenance into Whimsy.  Some of
>> the key things I want to improve upon is the overall experience around
>> managing the podling.  Sam's done a great job with rosters, but we can
>> start to track other things in whimsy, which mirrors what's in the status
>> file.  This can include IP Clearance/SGAs, Podling Name Searches, the
>> various dates we track.
>> 
>> Ultimately, I want to simplify how podlings are managed and make it a bit
>> easier on an end user.  Rather than needing to svn checkout to get files,
>> they simply go to a webpage, and assuming they're on that podling's roster
>> they would have access to update the status.  We could even automate
>> certain events so that when the board passes a resolution to graduate the
>> podling, the status file is updated along side any other record the podling
>> may have.
>> 
>> This does mean that the status file format is likely to change.  It also
>> means we're likely to move away from the java based build tool that has to
>> parse the XML templates into web pages and instead rely on a more
>> structured format for the status.
>> 
>> It doesn't mean you have to change.  If you like using SVN to edit this
>> stuff that's fine, you would still be able to.  Just what you're editing is
>> likely to be different.
>> 
>> Thoughts? Opinions?
>> 
>> John
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Emailing images.

[Felix Meschberger]

Hi

Confluence/Wiki is used by some. For example in Sling we have an area where new 
concepts are written to be discussed.

Regards
Felix

Von meinem iPad gesendet

> Am 31.05.2017 um 18:57 schrieb James Bognar :
> 
> Since images are lost on apache emails, what have other teams done if they
> want to include images on messages to their dev list account?
> 
> What are our options?  Upload to Imgur and attach URL?  Other ideas?

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Good examples of licensing in ASF produced web apps?

[Felix Meschberger]

Hi Roman

As has been mentioned by others, I would not think there is any relaxation. At 
the end of the day, it is something we build and distribute. So not having 
appropriate LICENSE and NOTICE (and probably DEPENDENCIES) is a no-go.

Having said that: The default Maven WAR plugin is just bundling the transitive 
clousure dependencies of the project, which if you don’t pay attention is half 
of the internet. JAR hell live.

Apache Sling also distributes WAR files. The difference here is that it is 
built with a custom-built plugin because essentially Sling only uses the 
servlet container as a container and manages its own deployment through an OSGi 
framework.

For example 
http://www-eu.apache.org/dist/sling/org.apache.sling.launchpad-8-webapp.war

Regards
Felix

Am 26.05.2017 um 23:49 schrieb Roman Shaposhnik 
>:

Hi!

I advising a podling on producing a binary release that
includes a Java web app (think war file). I wanted to give
them a taste of what TLPs do so I went to the ones that
I knew were generating war files: Oozie and Ranger.
You know the stuff I'm familiar with in Hadoop ecosystem.

What he discovered may shock you! No, but seriously.

Here's what these projects publish on Maven central:

https://search.maven.org/remotecontent?filepath=org/apache/oozie/oozie-webapp/4.3.0/oozie-webapp-4.3.0.war
https://search.maven.org/remotecontent?filepath=org/apache/ranger/security-admin-web/0.7.0/security-admin-web-0.7.0.war

Each of these WAR files:
  1. bundles all sorts of dependancies -- not just the bits coming
   from the project itself

   2. Neither provides a meanigful LICENSE nor NOTICE files.
   The ones under ./WEB-INF/classes/META-INF are stock ones
   and really don't address the binary dependencies bundling

Have we somehow relaxed the requirements for binary artifacts?
I hope not -- and if not -- what are the good examples of web app
projects doing it right?

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Revisit policy that all IPMC members have commit privs to all incubator repositories.

[Felix Meschberger]

Hi

I think this sounds very reasonable.

+1

Regards
Felix

> Am 06.04.2017 um 07:06 schrieb Sam Ruby :
> 
> Background, from https://issues.apache.org/jira/browse/INFRA-13804
> 
>> With this feedback and review, I believe we're still operating as expected.
>> 
>> * Per current policy, IPMC members have commit privileges on all Incubator 
>> repositories.
>> * The above is effected through the use of a private GitHub Team
>> * According to users' GitHub preferences, they will Watch new repositories
>> * GitHub is sending notifications of changes, per Watch selections
>> 
>> The "answer" here is to Unwatch repositories, as appropriate, and/or
>> to alter the GitHub user account preference for auto-Watching new
>> repositories.
> 
> Here's my case:
> 
> I believe that asking all IPMC members that request access to *any* ASF 
> github repository to get notification emails on *all* incubator projects that 
> participate in the gitbox experiment is unreasonable.
> 
> I believe that asking all IPMC members to individually unwatch each and every 
> repository as they are created is unreasonable.
> 
> I believe that asking all IPMC members to uncheck "Automatically watch" is 
> unreasonable as it (a) will result in people being notified for new 
> repositories that they should be watching, and (b) presumes that people are 
> not participating/watching in other non-ASF GitHub repositories.
> 
> Accordingly, Since I do believe that it is reasonable for every ASF member to 
> get email on all ASF repositories that they have commit privileges to, I am 
> asking that the IPMC revisit the current policy that all IPMC members have 
> commit privileges on all Incubator repositories.
> 
> I believe that the alternative is technically feasible: have each podling 
> manage a list of committers for that podling:
> 
> https://whimsy.apache.org/roster/ppmc/
> 
> - Sam Ruby
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Return Log4cxx to the Logging Services project

[Felix Meschberger]

+1

Regards
Felix

> Am 11.03.2017 um 09:31 schrieb Ralph Goers :
> 
> Log4cxx was originally a sub-project of the Logging Services. In 2013 several 
> users became frustrated that they were submitting patches but there were no 
> committers who could apply them. The Logging Services PMC was not comfortable 
> making them committers as that would have given them commit rights to all the 
> Logging Services projects, which at that time were all hosted in Subversion. 
> As a consequence Log4cxx became an incubator project in hopes those who had 
> expressed interest would start actively contributing to the project. After 3 
> 1/2 years this has not had the hoped for result, although it does have more 
> activity than it did prior to entering the incubator.
> 
> The Logging Services PMC believes there is no longer a point to having 
> Log4cxx remain in the incubator. The one active committer on Log4cxx has been 
> voted in as a Logging Services committer and the PMC has voted [1] to move 
> the project back to Logging Services. This is a vote for the incubator to 
> affirm that move. 
> 
> [] +1 Move the project back to Logging Services
> [] +0 I don’t care where the project resides
> [] -1 The project should remain in the incubator because …
> 
> 
> [1] 
> https://mail-search.apache.org/pmc/private-arch/logging-private/201703.mbox/browser
>  
> 

Re: [REQUEST] Please add PR-related item to podling graduation checklist

[Felix Meschberger]

+1

This makes a lot of sense.

Thanks
Felix

> Am 27.01.2017 um 02:09 schrieb Sally Khudairi :
> 
> Hello Apache Incubator team --I hope you are all well.
> John Ament (copied) suggested I write to you regarding promoting a podling's 
> graduation.
> Would it be possible to include a line item somewhere on 
> http://incubator.apache.org/guides/graduation.html along the lines of: 
>> "PPMCs: please contact ASF Marketing & Publicity at press(at)apache(dot)org 
>> if your project is interested in a formal press release announcing your 
>> graduation."
> 
> I ask because we need enough time to prepare press releases, getting 
> testimonials, editing/review process, etc. And example of a TLP press release 
> is https://s.apache.org/u67z
> Too often what's happening is that once the submission request to the Board 
> goes out, the podling starts tweeting that they're graduating 
> (incorrect/inappropriate). Or that they're up for graduation (OK, but iffy).
> When the Board passes the resolution, everyone tweets. OK, fine, it's time to 
> celebrate.
> 
> Then the project comes to me saying "oops: we need press..." and I wind up 
> scrambling to get everything done in a timely manner so that the press 
> release doesn't happen weeks after the Board passes the resolution (= no 
> longer "news").
> The past several press releases that have gone out are a result of me seeing 
> that the podling's proposal has gone to board@, and me writing the VP 
> stating, "I see that you're preparing to graduate. Do you want a press 
> release? If so, let's work together ..."
> 
> Seeing that most podlings need a couple of weeks to pull their content 
> together --particularly if soliciting supporting testimonials from the 
> community-- starting our preparations as part of their graduation checklist 
> would be hugely helpful.
> And, even if the graduation doesn't happen for some reason, at least we're 
> ready.
> 
> Thanks in advance for your consideration. I look forward to hearing from you!
> Kind regards,Sally
> Vice President Marketing & PublicityThe Apache Software Foundation = = = = =  
> vox +1 617 921 8656gvox +1 646 598 4616skype sallykhudairi


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: LDAP changes to support podlings

[Felix Meschberger]

Hi Sam

Like this very much. Thanks !

Started doing that for OpenWhisk and realized some strange UI behaviour: To add 
a PPMC member I have to click + then search for the user, click on + again and 
then click on „Add to PPMC“ button

What is the reason for the last „Add to PPMC“ button click ? This somehow 
breaks the otherwise nice experience. Or would it be possible to batch-add 
multiple members ?

Thanks
Felix

> Am 18.01.2017 um 17:07 schrieb Sam Ruby :
> 
> On Mon, Jan 16, 2017 at 1:05 PM, Sam Ruby  wrote:
>> Current status: for ppmcs that have lists in the subversion puppet
>> definitions, those lists have been loaded into LDAP, and augmented with
>> mentor information from podlings.xml.  A list of all current podlings can be
>> found here, and those that have been loaded contain links to individual
>> pages:
>> 
>> https://whimsy.apache.org/roster/ppmc/
>> 
>> These pages are currently read-only, and contain links to the project page,
>> mailing lists, and prior published reports.
> 
> These pages are now live.  If you are a mentor of a podling, please go
> in and add ppmc members.  Or add one ppmc member and ask them to add
> the rest.  :-)  Or simply verify that the list is accurate if it was
> seeded from the authentication lists in the puppet configuration.
> 
> Note: for the moment, private@incubator will be copied on all changes.
> Once things have been verified as working, this will be removed.
> 
> - Sam Ruby
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DRAFT] Incubator PMC Board Report - January 2017

[Felix Meschberger]

Hi

Hmm, I see OpenWhisk missing here. I know the community had an edit last week 
and Matt tried to update …

Will check back with the poddling.

Regards
Felix

> Am 09.01.2017 um 02:05 schrieb John D. Ament :
> 
> All,
> 
> Below is the current draft of the IPMC board report.  Please review it for
> accurancy and make changes on https://wiki.apache.org/incubator/January2017
> if needed.
> 
> One call out - many podlings have very few mentor sign offs.  Would be good
> to get more mentors looking at the reports.
> 
> John
> 
> ---
> 
> Incubator PMC report for January 2017
> 
> The Apache Incubator is the entry path into the ASF for projects and
> codebases wishing to become part of the Foundation's efforts.
> 
> There are presently 64 podlings incubating.  We had one new podling join.
> No changes in PMC membership.
> 
> * Community
> 
>  New IPMC members:
> 
>  - None
> 
>  People who left the IPMC:
> 
>  - None
> 
> * New Podlings
> 
>  - Griffin
> 
> * Graduations
> 
>  The board has motions for the following:
> 
>  - Ranger?
> 
> * Releases
> 
>  The following releases entered distribution during the month of
>  December:
> 
>  - Apache Mynewt1.0.0-b1-incubating  2016-12-12
>  - Apache Edgent1.0.0-incubating 2016-12-15
>  - Apache Tephra0.10.0-incubating2016-12-15
>  - Apache Fineract  0.5.0-incubating 2016-12-22
>  - Apache Streams   0.4.1-incubating 2016-12-26
>  - Apache Guacamole 0.9.10-incubating2016-12-29
> 
> 
> * IP Clearance
> 
>  - None
> 
> * Legal / Trademarks
> 
>  - The process for picking a new incubator logo has begun, we're expecting
> to complete it in April.  Thanks to Sally for picking up the CFP!
>  - Incubator documentation updates are in progress, we are starting with
> release management then will move into roles & responsibilities.
> 
> 
> * Infrastructure
> 
>  - No issues, though its suspected some status on github as master for
> OpenWhisk may be expected.
> 
> * Miscellaneous
> 
>  - N/A
> 
> * Credits
> 
>  - Report Manager: John D. Ament
> 
>  Summary of podling reports 
> 
> * Still getting started at the Incubator
> 
>  - NetBeans
>  - RocketMQ
>  - Traffic Control
>  - Weex
> 
> * Not yet ready to graduate
> 
>  No release:
> 
>  - Annotator
>  - MADlib
>  - ODF Toolkit
> 
>  Community growth:
> 
>  - Gossip
>  - Horn
>  - Juneau
>  - Mynewt
> 
>  Need Signoffs:
> 
>  - HAWQ
>  - Annotator
>  - Hivemall
>  - MADlib
>  - NetBeans
> 
> * Ready to graduate
> 
>  The Board has motions for the following:
> 
>  - Ranger?
> 
>  The following appear to be close from maturity model:
> 
>  - Airflow
>  - BatchEE
>  - FreeMarker
>  - Metron
> 
> * Did not report, expected next month
> 
>  - DataFu
>  - Milagro
>  - OpenWhisk
>  - SensSoft
> 
> 
> --
>   Table of Contents
> Airflow
> Annotator
> BatchEE
> FreeMarker
> Gossip
> HAWQ
> Hivemall
> HORN
> Juneau
> MADlib
> Metron
> Mynewt
> NetBeans
> ODF Toolkit
> RocketMQ
> Rya
> Spot
> Traffic Control
> Weex
> 
> --
> 
> 
> 
> Airflow
> 
> Airflow is a workflow automation and scheduling system that can be used to
> author and manage data pipelines.
> 
> Airflow has been incubating since 2016-03-31.
> 
> Three most important issues to address in the move towards graduation:
> 
>  1. Getting an Apache release out
>  2.
>  3.
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> 
> None
> 
> How has the community developed since the last report?
> 1. We elected 1 new PPMC Member/Committer : Alex Van Boxel a.k.a.
> alexvanboxel
> 2. Since our last podling report 3 months ago (i.e. between Oct 4 and Dec
> 31, inclusive), we grew our contributors from 191 to 224
> 3. Since our last podling report 3 months ago (i.e. between Oct 4 and Dec
> 31, inclusive), we resolved 202 pull requests (currently at 1263 closed
> PRs)
> 4. One meet-up, hosted at WePay, was held by the community
> 5. Since being accepted into the incubator, the number of companies
> officially using Apache Airflow has risen from 30 to 74
> 
> 
> How has the project developed since the last report?
> See above
> 
> 
> Date of last release:
> 
>  None.  First ASF release currently being discussed.
> 
> When were the last committers or PPMC members elected?
> 
> As mentioned on
> https://cwiki.apache.org/confluence/display/AIRFLOW/Announcements#Announcements-Nov28,2016,
> Alex Van Boxel joined the Apache Airflow PPMC/Committer group.
> 
> 
> Signed-off-by:
> 
>  [X](airflow) Chris Nauroth
>  [x](airflow) Hitesh Shah
>  [ ](airflow) Jakob Homan
> 
> Shepherd/Mentor notes:
> 
> 
> 
> 
> Annotator
> 
> Annotator provides annotation enabling code for browsers, servers, and
> humans.
> 
> Annotator has been incubating since 2016-08-30.
> 
> Three 

Re: [DISCUSS] publishing docker image for podling

[Felix Meschberger]

Hi

Deploying containers to Docker hub IMHO is the same as deploying Java artefacts 
to Maven or Node.JS modules to NPM or whatever. It is a release of a 
convenience binary in addition to the official source release.

As such:

+1 to supporting Docker, just like Maven Repositories or NPM repositories for 
convenience binaries of releases

+1 to not requiring the „incubator“ suffix or prefix (similar to referred to 
Maven discussion)

+1 to requiring notes regarding incubation of the respective notes in any 
Docker Hub description functionality (see for example 
https://hub.docker.com/r/nuagebec/ubuntu/)

Regards
Felix


Am 05.01.2017 um 10:32 schrieb Greg Stein 
>:

Taking off my Infrastructure hat from within that issue, and speaking to
this from a Foundation policy standpoint ... I think this is probably okay,
if the docker image is named (say) u/apache/incubator-singa. We allow
incubator projects in our github namespace as
github.com/apache/incubator-singa.

But then we also get into an area of "what happens around graduation?" ...
do we then offer both u/incubator-singa *and* u/singa ? ... If that's
acceptable, then this may be a simple decision. But for downstream
stability/continuity reasons would a podling want to *start* at
docker/u/singa ? ... and that is where I ask if the IPMC is willing to give
up the incubator- signal within our namespace on docker.

And yes, I recognize the similarity to the concurrent discussion about
Maven Central artifacts. There are costs/benefits around continuity and
impacts on downstream users.

Putting my Infra hat back on: the IPMC needs to specify a policy on
allowance and naming around hub.docker.com hosting, that 
Infra will use to
assist podlings.

Cheers,
Greg Stein
Infrastructure Administrator, ASF


On Thu, Jan 5, 2017 at 12:11 AM, Thejas Nair 
> wrote:

As per Greg Stein's comment in
https://issues.apache.org/jira/browse/INFRA-13156, we haven't had any
podling request for a docker image (aka a "convenience binary") to be
published within Apache's namespace in hub.docker.com .

Starting this thread to see if we should have a vote on for this or we can
get incubator VP approval for this.

Thanks,
Thejas

Re: [VOTE] Drop incubating requirement of Maven artifacts

[Felix Meschberger]

+1 (binding)

A policy (or rule or whatever it is that creates expectations) which just 
applies to a single build toolchain does not make any sense at all. So lets 
trash this.

Regards
Felix


> Am 02.01.2017 um 18:22 schrieb John D. Ament :
> 
> All,
> 
> I'm calling to vote on a proposed policy change.  Current guide at [1]
> indicates that maven artifacts should include incubator (or incubating) in
> the version string of maven artifacts.  Its labeled as a best practice, not
> a requirement and is not a policy followed on other repository management
> tools (e.g. PyPi).
> 
> I therefore push forward that the incubator will cease expecting java-based
> projects to publish artifacts with "-incubating" in the version string,
> with the understanding that:
> 
> - Incubating is a term used to refer to a project's stability, not a
> release's stability.  It is generally understood that incubating projects
> are not necessarily immature, but may have a potential of failing to become
> a TLP.
> - Podling releases are endorsed, the podling itself is not endorsed.  We
> will not approve releases that are blatantly against ASF policies.
> 
> 
> [ ] +1 Drop the -incubator/-incubating expectation of maven projects
> [ ] +/0
> [ ] -1 Don't drop because
> 
> 
> [1]:
> http://incubator.apache.org/guides/release-java.html#best-practice-maven


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Incubator PMC Board Report - December 2016

[Felix Meschberger]

Hi John

Good. Thanks for clarifying. Will add an OpenWhisk section then.

Re DNS: Yes, saw that. Thanks. So still waiting for the lists to be confirmed.

Regards
Felix

> Am 30.11.2016 um 14:22 schrieb John D. Ament <johndam...@apache.org>:
> 
> Felix,
> 
> This is an area that unfortunately isn't written too well and at least to
> me should be a more formal policy.
> 
> Podlings are encouraged to report their first month.  Their first month is
> very simple - not a lot of progress, just getting started.  You may want to
> confirm that things like mailing lists are online, website is starting, SGA
> in proc, ICLAs/CCLAs are in flight as well.  I'm not sure if you saw the
> ticket I pinged you in, INFRA took care of the DNS for you last night.
> 
> Podling reporting group is based on the month they join the incubator, e.g.
> Feb, May, Aug and Nov should be reporting group 3, monthly Dec - Feb.  You
> may want to double check that, I'm not sure why you're listed as group 1.
> 
> John
> 
> On Wed, Nov 30, 2016 at 7:53 AM Felix Meschberger <fmesc...@adobe.com>
> wrote:
> 
>> A question on procedure for OpenWhisk: We just entered and according to
>> podlings.xml we are to report in December while the template just lists us
>> as having entered.
>> 
>> I would like to have a clarification: Are we to report ? Else I’d just
>> adapt the podlings.xml to change our initial monthlies to be January,
>> February, and March.
>> 
>> Thanks
>> Felix
>> 
>>> Am 30.11.2016 um 12:42 schrieb John D. Ament <johndam...@apache.org>:
>>> 
>>> December 2016 Incubator report timeline:
>>> 
>>>   https://wiki.apache.org/incubator/December2016
>>> 
>>>   Wed December 07 -- Podling reports due by end of day
>>>   Sun December 11 -- Shepherd reviews due by end of day
>>>   Sun December 11 -- Summary due by end of day
>>>   Tue December 13 -- Mentor signoff due by end of day
>>>   Wed December 14 -- Report submitted to Board
>>>   Wed December 21 -- Board meeting
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 

Re: Incubator PMC Board Report - December 2016

[Felix Meschberger]

A question on procedure for OpenWhisk: We just entered and according to 
podlings.xml we are to report in December while the template just lists us as 
having entered.

I would like to have a clarification: Are we to report ? Else I’d just adapt 
the podlings.xml to change our initial monthlies to be January, February, and 
March.

Thanks
Felix

> Am 30.11.2016 um 12:42 schrieb John D. Ament :
> 
> December 2016 Incubator report timeline:
> 
>https://wiki.apache.org/incubator/December2016
> 
>Wed December 07 -- Podling reports due by end of day
>Sun December 11 -- Shepherd reviews due by end of day
>Sun December 11 -- Summary due by end of day
>Tue December 13 -- Mentor signoff due by end of day
>Wed December 14 -- Report submitted to Board
>Wed December 21 -- Board meeting


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept OpenWhisk into the Apache Incubator

[Felix Meschberger]

+1

Regards
Felix

> Am 17.11.2016 um 07:22 schrieb Sam Ruby <ru...@intertwingly.net>:
> 
> Now that the discussion thread on the OpenWhisk Proposal has died
> down, please take a moment to vote on accepting OpenWhisk into the
> Apache Incubator.
> 
> The ASF voting rules are described at:
>   http://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote
> for which only Incubator PMC member votes are binding.
> 
> Votes from other people are also welcome as an indication of peoples
> enthusiasm (or lack thereof).
> 
> Please do not use this VOTE thread for discussions.
> If needed, start a new thread instead.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept OpenWhisk into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept OpenWhisk into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
>   https://wiki.apache.org/incubator/OpenWhiskProposal
> 
> - Sam Ruby
> 
> = OpenWhisk Proposal =
> 
> OpenWhisk is an open source, distributed Serverless computing platform
> able to execute application logic (Actions) in response to events
> (Triggers) from external sources (Feeds) or HTTP requests governed by
> conditional logic (Rules). It provides a programming environment
> supported by a REST API-based Command Line Interface (CLI) along with
> tooling to support packaging and catalog services.
> 
> Champion: Sam Ruby, IBM
> 
> Mentors:
> * Felix Meschberger, Adobe
> * Isabel Drost-Fromm, Elasticsearch GmbH
> * Sergio Fernández, Redlink GmbH
> 
> == Background ==
> 
> Serverless computing is the evolutionary next stage in Cloud computing
> carrying further the abstraction offered to software developers using
> Container-based operating system virtualization. The Serverless
> paradigm enables programmers to just “write” functional code and not
> worry about having to configure any aspect of a server needed for
> execution. Such Serverless functions are single purpose and stateless
> that respond to event-driven data sources and can be scaled on-demand.
> 
> The OpenWhisk project offers a truly open, highly scalable, performant
> distributed Serverless platform leveraging other open technologies
> along with a robust programming model, catalog of service and event
> provider integrations and developer tooling.
> Specifically, every architectural component service of the OpenWhisk
> platform (e.g., Controller, Invokers, Messaging, Router, Catalog, API
> Gateway, etc.) all is designed to be run and scaled as a Docker
> container. In addition, OpenWhisk uniquely leverages aspects of Docker
> engine to manage, load balance and scale supported OpenWhisk runtime
> environments (e.g., JavaScript, Python, Swift, Java, etc.), that run
> Serverless functional code within Invoker compute instances, using
> Docker containers.
> 
> OpenWhisk's containerized design tenants not only allows it to be
> hosted in various IaaS, PaaS Clouds platforms that support Docker
> containers, but also achieves the high expectation of the Serverless
> computing experience by masking all aspects of traditional resource
> specification and configuration from the end user simplifying and
> accelerating Cloud application development.
> In order to enable HTTP requests as a source of events, and thus the
> creation of Serverless microservices that expose REST APIs, OpenWhisk
> includes an API Gateway that performs tasks like security, request
> routing, throttling, and logging.
> 
> == Rationale ==
> 
> Serverless computing is in the very early stages of the technology
> adoption curve and has great promise in enabling new paradigms in
> event-driven application development, but current implementation
> efforts are fractured as most are tied to specific Cloud platforms and
> services. Having an open implementation of a Serverless platform, such
> as OpenWhisk, available and governed by an open community like Apache
> could accelerate growth of this technology, as well as encourage
> dialog and interoperability.
> 
> Having the ASF accept and incubate OpenWhisk would provide a clear
> signal to developers interested in Serverless and its future that they
> are welcome to participate and contribute in its development, growth
> and governance.
> 
> In addition, there are numerous projects already at the ASF that would
> provide a natural fit to the API-centric, event-driven programming
> model that OpenWhisk sees as integral to a Serverless future. In fact,
> any project that includes a service that can produce or consume
> actionable events could become an integration point with
> OpenWhi

Re: [DISCUSS] OpenWhisk Proposal

[Felix Meschberger]

Hi Edward

Absolutely. Thanks for adding yourself.

Regards
Felix

> Am 07.11.2016 um 21:11 schrieb Edward J. Yoon <edwardy...@apache.org>:
> 
> Awesome. Let me in.
> 
> On Fri, Nov 4, 2016 at 10:35 PM, Felix Meschberger <fmesc...@adobe.com> wrote:
>> Hi all
>> 
>> I have made some additions to the OpenWhisk Proposal [1]:
>> 
>> - restructured the API Gateway references: It is expected
>>   that the API Gateway will be refactored with additional
>>   code donated by IBM during incubation.
>> - added a note on the API Gateway’s dependency on OpenSSL
>> - added a note on Trademarks IBM is currently pursuing and
>>   intends to transfer to ASF
>> - fixed some typos
>> 
>> With these changes and no discussions over the course of the recent weeks, I 
>> would propose we could could vote for OpenWhisk to become an incubating 
>> project over the course of next weeks.
>> 
>> Of course we are still open to welcome interested people to become initial 
>> committers to OpenWhisk Servlerless Runtime and API Gateway !
>> 
>> WDYT ?
>> 
>> Regards
>> Felix
>> 
>> [1] https://wiki.apache.org/incubator/OpenWhiskProposal
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
> 
> -- 
> Best Regards, Edward J. Yoon
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [DISCUSS] OpenWhisk Proposal

[Felix Meschberger]

Hi Sergio

Pleased to meet you and thanks for offering to become a mentor. That helps.

Feel free to add yourself to the proposal

Thanks
Felix

Am 04.11.2016 um 15:57 schrieb Sergio Fernández 
<wik...@apache.org<mailto:wik...@apache.org>>:

Hi Felix,

most of the ASF project have successfully manage to keep using GitHub for
PRs, having the master git repository in ASF-controlled infrastructure. In
the end it doesn't represent that big break on the common workflows. But
definitely something the podling could try to address during incubation.

I'd be happy to jump-in the proposal and help as mentor.

Cheers,


On Fri, Nov 4, 2016 at 3:48 PM, Felix Meschberger 
<fmesc...@adobe.com<mailto:fmesc...@adobe.com>>
wrote:

Hi John

My understanding is, that we are well aware of this concern, which others
have mentioned as well.

Also Greg noted in the proposal:

gstein sez: the podling can only graduate within an approved repository
system. The IPMC may have a differing opinion, but from an Infra
perspective: the OpenWhisk podling can continue with their usage of a
GitHub repository, but faces a clear obstacle: GitHub "as master [as
allowed by the Foundation]" must be approved and working before the
graduation, or they must migrate their primary to the Foundation's Git
repository (at git-wip) before they graduate.

I think this sounds like a good compromise to work on and the poddling
intends to work actively with Infra to see that we can stay in GitHub. If
that is not possible, we byte the bullet accordingly.

In addition, also according to Greg:

We require that anybody committing to a GitHub repository authenticates
with BOTH: GitHub, and the ASF. No commits without that multiple
authentication. (this is based on our current experiments with Whimsy and
Traffic Server; same rules would apply to this podling)

The original discussion took place after the initial submission, see [1]

Does that help ?

Regards
Felix

[1] https://lists.apache.org/thread.html/1c22a29b69e944ee725278aae05bd4
1dea80d10d0d204c26eb4cb24c@%3Cgeneral.incubator.apache.org<http://3Cgeneral.incubator.apache.org>%3E

Am 04.11.2016 um 15:20 schrieb John D. Ament 
<johndam...@apache.org<mailto:johndam...@apache.org>>:

I raised the concern over using github as the primary repo.  This is
still
unresolved, as I understood it.

John

On Fri, Nov 4, 2016 at 9:36 AM Felix Meschberger 
<fmesc...@adobe.com<mailto:fmesc...@adobe.com>>
wrote:

Hi all

I have made some additions to the OpenWhisk Proposal [1]:

- restructured the API Gateway references: It is expected
 that the API Gateway will be refactored with additional
 code donated by IBM during incubation.
- added a note on the API Gateway’s dependency on OpenSSL
- added a note on Trademarks IBM is currently pursuing and
 intends to transfer to ASF
- fixed some typos

With these changes and no discussions over the course of the recent
weeks,
I would propose we could could vote for OpenWhisk to become an
incubating
project over the course of next weeks.

Of course we are still open to welcome interested people to become
initial
committers to OpenWhisk Servlerless Runtime and API Gateway !

WDYT ?

Regards
Felix

[1] https://wiki.apache.org/incubator/OpenWhiskProposal
-
To unsubscribe, e-mail: 
general-unsubscr...@incubator.apache.org<mailto:general-unsubscr...@incubator.apache.org>
For additional commands, e-mail: 
general-h...@incubator.apache.org<mailto:general-h...@incubator.apache.org>





--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co<mailto:sergio.fernan...@redlink.co>
w: http://redlink.co<http://redlink.co/>

Re: [DISCUSS] OpenWhisk Proposal

[Felix Meschberger]

Hi John

My understanding is, that we are well aware of this concern, which others have 
mentioned as well.

Also Greg noted in the proposal:

> gstein sez: the podling can only graduate within an approved repository 
> system. The IPMC may have a differing opinion, but from an Infra perspective: 
> the OpenWhisk podling can continue with their usage of a GitHub repository, 
> but faces a clear obstacle: GitHub "as master [as allowed by the Foundation]" 
> must be approved and working before the graduation, or they must migrate 
> their primary to the Foundation's Git repository (at git-wip) before they 
> graduate. 

I think this sounds like a good compromise to work on and the poddling intends 
to work actively with Infra to see that we can stay in GitHub. If that is not 
possible, we byte the bullet accordingly.

In addition, also according to Greg:

> We require that anybody committing to a GitHub repository authenticates with 
> BOTH: GitHub, and the ASF. No commits without that multiple authentication. 
> (this is based on our current experiments with Whimsy and Traffic Server; 
> same rules would apply to this podling) 

The original discussion took place after the initial submission, see [1]

Does that help ?

Regards
Felix

[1] 
https://lists.apache.org/thread.html/1c22a29b69e944ee725278aae05bd41dea80d10d0d204c26eb4cb24c@%3Cgeneral.incubator.apache.org%3E

> Am 04.11.2016 um 15:20 schrieb John D. Ament <johndam...@apache.org>:
> 
> I raised the concern over using github as the primary repo.  This is still
> unresolved, as I understood it.
> 
> John
> 
> On Fri, Nov 4, 2016 at 9:36 AM Felix Meschberger <fmesc...@adobe.com> wrote:
> 
>> Hi all
>> 
>> I have made some additions to the OpenWhisk Proposal [1]:
>> 
>> - restructured the API Gateway references: It is expected
>>   that the API Gateway will be refactored with additional
>>   code donated by IBM during incubation.
>> - added a note on the API Gateway’s dependency on OpenSSL
>> - added a note on Trademarks IBM is currently pursuing and
>>   intends to transfer to ASF
>> - fixed some typos
>> 
>> With these changes and no discussions over the course of the recent weeks,
>> I would propose we could could vote for OpenWhisk to become an incubating
>> project over the course of next weeks.
>> 
>> Of course we are still open to welcome interested people to become initial
>> committers to OpenWhisk Servlerless Runtime and API Gateway !
>> 
>> WDYT ?
>> 
>> Regards
>> Felix
>> 
>> [1] https://wiki.apache.org/incubator/OpenWhiskProposal
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 

[DISCUSS] OpenWhisk Proposal

[Felix Meschberger]

Hi all

I have made some additions to the OpenWhisk Proposal [1]:

 - restructured the API Gateway references: It is expected
   that the API Gateway will be refactored with additional
   code donated by IBM during incubation.
 - added a note on the API Gateway’s dependency on OpenSSL
 - added a note on Trademarks IBM is currently pursuing and
   intends to transfer to ASF
 - fixed some typos

With these changes and no discussions over the course of the recent weeks, I 
would propose we could could vote for OpenWhisk to become an incubating project 
over the course of next weeks.

Of course we are still open to welcome interested people to become initial 
committers to OpenWhisk Servlerless Runtime and API Gateway !

WDYT ?

Regards
Felix

[1] https://wiki.apache.org/incubator/OpenWhiskProposal
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Request to edit OpenWhiskProposal

[Felix Meschberger]

Thanks, works.

Regards
Felix

> Am 04.11.2016 um 13:27 schrieb Bertrand Delacretaz <bdelacre...@apache.org>:
> 
> On Fri, Nov 4, 2016 at 12:59 PM, Felix Meschberger <fmesc...@adobe.com> wrote:
>> ...Can it please be reestablished for user FelixMeschberger ? ...
> 
> You should be good now.
> -Bertrand
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Request to edit OpenWhiskProposal

[Felix Meschberger]

Hi

As a mentor I have to add some updates to the OpenWhiskProposal but it looks 
like my editing karma has been revoked.

Can it please be reestablished for user FelixMeschberger ?

Thanks
Felix
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [discuss] Apache OpenWhisk Incubator Proposal

[Felix Meschberger]

Hi Mark

Understood. And these are valid points to be discussed in the larger context of 
whether ASF supports GitHub as a primary repository. Which in turn is outside 
of the scope of this proposal. And which is where this OpenWhiz community will 
have a vested interest in participating.

And as Greg already added a comment to the proposal, would it be ok to get back 
to the technical merrit of this proposal and not loose ourselves in the 
discussion over whether GitHub is ok or not ? Thanks.

Regards
Felix

> Am 14.10.2016 um 15:37 schrieb Mark Struberg <strub...@yahoo.de.INVALID>:
> 
> The problem with github is that we (ASF) cannot give any guarantees if the 
> main stuff doesn't originate from our own hardware.
> 
> Not whether the ticket system doesn't loose all tickets (didn't that happen 
> in the past?) nor whether really only IP clean stuff got committed.
> You e.g. have no clue if someone else uses your email and name in a commit 
> and pushes it.
> Everyone else can create a commit with your email and name in GIT, there is 
> no check. And when pulling in changes, a faked one might get piggy packed and 
> introduce a backdoor. I know this might be close to paranoid but it is 
> theoretically possible.
> 
> 
> 
> The workflow with git hosted @ASF is btw pretty much exactly the same for 
> committers. And a PR integration does exist as well. So I don't see what you 
> miss?
> 
> LieGrue,
> strub
> 
> 
> 
> 
>> On Friday, 14 October 2016, 13:52, Felix Meschberger <fmesc...@adobe.com> 
>> wrote:
>>> Hi John
>> 
>> This also ties into Mark’s question earlier on.
>> 
>> The OpenWhisk part of the proposal is currently being developed in GitHub 
>> and 
>> the developers are used to the GitHub flow and features including but not 
>> limited to GitHub Issues.
>> 
>> We have discussed this topic before proposing the project and we are all 
>> aware 
>> on the caveats. But as we write in the proposal, we intend to work with 
>> infra 
>> and other stakeholders to have repositories in GitHub accepted as primary 
>> work 
>> repositories before graduation.
>> 
>> Hope that helps.
>> 
>> Regards
>> Felix
>> 
>> 
>>> Am 14.10.2016 um 12:50 schrieb John D. Ament <johndam...@apache.org>:
>>> 
>>> Sam,
>>> 
>>> Can your or someone representing the proposed podling explain why using
>>> github as master is preferable to the current mirror strategy in use?
>>> 
>>> John
>>> 
>>> On Fri, Oct 14, 2016 at 6:29 AM Sam Ruby <ru...@intertwingly.net> 
>> wrote:
>>> 
>>>> On Fri, Oct 14, 2016 at 1:31 AM, Greg Stein <gst...@gmail.com> 
>> wrote:
>>>>> On Thu, Oct 13, 2016 at 3:27 PM, Sam Ruby 
>> <ru...@intertwingly.net>
>>>> wrote:
>>>>> 
>>>>>> Hello everyone,
>>>>>> 
>>>>>> Attached to this message is a proposed new project - Apache 
>> OpenWhisk.
>>>>>> 
>>>>>> The text of the proposal is included below. Additionally, the 
>> proposal
>>>> is
>>>>>> in draft form on the Wiki, where we will make any required 
>> changes:
>>>>>> 
>>>>>> https://wiki.apache.org/incubator/OpenWhiskProposal
>>>>>> 
>>>>>> We look forward to your feedback and input.
>>>>> 
>>>>> OpenWhisk has a first-time-unique request on its Git repository 
>> request.
>>>> I
>>>>> inserted a comment about OpenWhisk's use of a GitHub repository 
>> [from
>>>>> Infra's standpoint], and the relation to the Foundation and a 
>> possible
>>>>> block on graduation.
>>>> 
>>>> If I could get some help in the form of an infrastructure team review
>>>> of the following plan, I would appreciate it:
>>>> 
>>>> 
>>>> 
>> https://lists.apache.org/thread.html/5b93ec0517ce7f90c0a467db9fc5e9cd087f1d4d9305c5491198b6c1@%3Cinfrastructure-private.apache.org%3E
>>>> 
>>>>> Thx,
>>>>> -g
>>>> 
>>>> - Sam Ruby
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>> 
>>>> 
>> 
>> B‹CB•È[œÝXœØÜšX™KK[XZ[ˆÙ[™\˜[][œÝXœØÜšX™P[˜ÝX˜]Ü‹˜\XÚK›Ü™ÃB‘›ÜˆY][Û˜[ÛÛ[X[™ËK[XZ[ˆÙ[™\˜[Z[[˜ÝX˜]Ü‹˜\XÚK›Ü™ÃB
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Re: [discuss] Apache OpenWhisk Incubator Proposal

[Felix Meschberger]

Hi John

This also ties into Mark’s question earlier on.

The OpenWhisk part of the proposal is currently being developed in GitHub and 
the developers are used to the GitHub flow and features including but not 
limited to GitHub Issues.

We have discussed this topic before proposing the project and we are all aware 
on the caveats. But as we write in the proposal, we intend to work with infra 
and other stakeholders to have repositories in GitHub accepted as primary work 
repositories before graduation.

Hope that helps.

Regards
Felix

> Am 14.10.2016 um 12:50 schrieb John D. Ament :
> 
> Sam,
> 
> Can your or someone representing the proposed podling explain why using
> github as master is preferable to the current mirror strategy in use?
> 
> John
> 
> On Fri, Oct 14, 2016 at 6:29 AM Sam Ruby  wrote:
> 
>> On Fri, Oct 14, 2016 at 1:31 AM, Greg Stein  wrote:
>>> On Thu, Oct 13, 2016 at 3:27 PM, Sam Ruby 
>> wrote:
>>> 
 Hello everyone,
 
 Attached to this message is a proposed new project - Apache OpenWhisk.
 
 The text of the proposal is included below. Additionally, the proposal
>> is
 in draft form on the Wiki, where we will make any required changes:
 
 https://wiki.apache.org/incubator/OpenWhiskProposal
 
 We look forward to your feedback and input.
>>> 
>>> OpenWhisk has a first-time-unique request on its Git repository request.
>> I
>>> inserted a comment about OpenWhisk's use of a GitHub repository [from
>>> Infra's standpoint], and the relation to the Foundation and a possible
>>> block on graduation.
>> 
>> If I could get some help in the form of an infrastructure team review
>> of the following plan, I would appreciate it:
>> 
>> 
>> https://lists.apache.org/thread.html/5b93ec0517ce7f90c0a467db9fc5e9cd087f1d4d9305c5491198b6c1@%3Cinfrastructure-private.apache.org%3E
>> 
>>> Thx,
>>> -g
>> 
>> - Sam Ruby
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 

Re: [VOTE] Flex to join the Apache Incubator

[Felix Meschberger]

+1
Regards
Felix
On 27.12.2011 10:51, Bertrand Delacretaz bdelacre...@apache.org wrote:

 Hi Incubator PMC members (*),

 I've just reviewed the [PROPOSAL] Flex for Apache Incubator thread
 and I think all relevant issues have been adressed now.

 I have added Anne and Dave Fisher as mentors, pending their final
 approval as Incubator PMC members. In the unlikely worst case that
 this approval doesn't happen the project has two confirmed mentors to
 start with anyway.

 Let's cast your votes to accept Flex as an incubating project,
 proposal is at http://wiki.apache.org/incubator/FlexProposal, copied
 below as well:

 [ ] +1 approve Flex as an incubating project.
 [ ] -1 reject (explaining why)
 [ ] +/- 0 don't care.

 This majority vote is open for 72 hours.

 Here's my +1.

 -Bertrand

 (*) although only votes from Incubator PMC members are binding,
 anybody is welcome to cast a vote

 ** Flex proposal copy ***

 = Apache Flex Proposal =

 == Abstract ==

 Apache Flex is an application framework for easily building
 Flash-based applications for mobile devices, the browser and desktop.

 == Proposal ==

 Apache Flex allows developers to target a variety of platforms,
 initially Apple iOS, Google Android, RIM !BlackBerry, Microsoft
 Windows, and Mac OS X with a single codebase. Flex provides a
 compiler, skinnable user-interface components and managers to handle
 styling, skinning, layout, localization, animation, module-loading and
 user interaction management.

 == Background ==

 Apache Flex is the software evolution of the popular Adobe Flex SDK
 project.
 Adobe Flex SDK evolved from the need to provide developers with an
 easy programming model for creating rich Internet applications that
 can run in the browser, on the desktop or on mobile devices.

 Adobe Flex SDK has always focused on a single goal: to provide
 application developers with all of the constructs needed to boost
 their productivity while building large-scale, visually expressive
 applications. This meant that Flex provided all the traditional UI
 components in a way that designers and developers could interact with
 them along with a dynamic scripting language, !ActionScript, and a
 declarative markup language, MXML.

 Adobe will donate the Flex trademark to the Apache Software Foundation
 as part of the incubation process. The source code, documentation and
 related assets will all be contributed to the Apache Foundation as
 Flex.

 == Rationale ==

 Content developers need to target multiple screens and the cost of
 creating applications native to every target platform is high.
 Additionally, the dominant window to the web is quickly becoming
 devices, mostly phones, and delivering consistent experiences is key.
 The Apache Flex project exists to bring the focus back to a consistent
 development model, one where a single application can run the exact
 same way across the web, desktop and mobile devices.

 == Initial Goals ==

  * Donate all Adobe Flex SDK source code and documentation to the
 Apache Software Foundation.
  * Setup and standardize the open governance of the Apache Flex project.
  * Rename all assets from Adobe Flex SDK to Apache Flex in project
 source code, docs, tests and related infrastructure.

 == Current Status ==

 Flex is a mature software project. 1.0 was shipped in March of 2004
 with 7 major releases having shipped since. The most recent release
 was the 4.6 version which shipped on November 29th, 2011.

 This proposal is currently being
 [[
 http://mail-archives.apache.org/mod_mbox/incubator-general/201112.mbox/%3CCB14DCA2.3885F%25aharui%40adobe.com%3E|discussed
 ]]
 on the incubator general mailing list, once that's done we'll ask the
 Incubator PMC to vote to accept it.

 == Meritocracy ==

 The Adobe Flex source code is available to the community on the Adobe
 opensource site:
 http://opensource.adobe.com/wiki/display/flexsdk/Flex+SDK.  Currently,
 while the community has been invited to contribute patches to the
 codebase, only Adobe employees decided on which patches to commit.
 There were no external committers and this caused frustration in the
 community.

 Going forward, both Adobe and our community are eager to become one
 single merit-based community working together.  To that end, Adobe
 employes only have a minority representation on the initial committers
 list.  Adobe is working to educate our community with meetings and
 blog posts on how the Apache model makes this possible for them.

 We have made it clear to our community that going forward, the
 community, rather than Adobe, will determine the future of Flex.

 == Community ==

 The community surrounding Flex is vast, diverse, distributed globally,
 and with all levels of proficiency in software development. The common
 thread of application development binds all Flex developers together.

 It is estimated that there is between 350,000 and 500,000 Flex
 developers worldwide. Precise numbers are impossible for us to know
 due to the 

Re: [VOTE] Accept Apache Callback for incubation

[Felix Meschberger]

+1 (binding)

Regards
Felix

Am 11.10.2011 um 23:09 schrieb Jukka Zitting:

 Hi,
 
 As discussed, the PhoneGap project would like to enter the Incubator
 under the Apache Callback name (potential alternative names to be
 discussed during incubation). The initial proposal has been well
 received and there are no major open issues, so it's time to vote!
 
 Thus I'm now calling a formal VOTE on the Apache Callback proposal as
 included below. The proposal is also available at
 http://wiki.phonegap.com/w/page/46311152/apache-callback-proposal on
 the PhoneGap wiki, and I'll place a copy for our archives on the
 Incubator wiki as soon as it stops giving me internal server errors.
 
 Please VOTE:
 
   [ ] +1 Accept Apache Callback for incubation
   [ ] -1  Don't accept Apache Callback for incubation because...
 
 This vote is open for the next 72 hours. Everyone is welcome to
 participate, but only votes from the Incubator PMC members are
 binding.
 
 Thanks! My vote is +1.
 
 Best regards,
 
 Jukka Zitting
 
 
 
 Apache Callback Proposal
 
 
 Abstract
 
 
 Apache Callback is a platform for building native mobile applications
 using HTML, CSS and JavaScript.
 
 Proposal
 
 
 Apache Callback allows web developers to natively target Apple iOS, Google
 Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia Symbian
 and Samsung Bada with a single codebase. The Callback APIs are based on
 open web standards. The Callback bridge technology enables access to native
 device capabilities. Utilizing the Callback bridge native plugins allow
 for any type of native access from the embedded webview.
 
 Background
 --
 
 Apache Callback is the free software evolution of the popular PhoneGap
 project.
 
 PhoneGap evolved from a hack that enabled a FFI (Foreign Function Interface)
 to an embedded WebView on iOS to a complete suite of tools for tackling
 parity across many mobile device and desktop platforms.
 
 PhoneGap has always focused on two complementary goals. Our first goal,
 is to see the web as a first class development platform. Not a sandbox
 without a filesystem but a real first class platform that includes access
 to the local system apis, sensors and data, in addition to first class
 tooling such as system debuggers. The second goal of PhoneGap  is for
 the project to cease to exist. This is not a nihilistic sentiment, rather
 we at the PhoneGap project are providing a reference implementation for
 web browsers to assist and guide the standardization process of browser APIs.
 
 The name and trademark of PhoneGap will become the commercial entity for
 the project. The source, code, documentation and related assets will all
 be contributed to the Apache Foundation as Callback.
 
 The Callback name comes from the event of the same name that is fired
 when the FFI bridge is established.
 
 Rationale
 -
 
 The dominate window to the web is quickly becoming devices, mostly phones.
 The manufacturers of devices, creators of mobile operating systems, and
 authors of web browsers are consolidating. (In many cases these are all
 already the same company.) Those stakeholders may see a future for the
 web but their bottom line is not necessarily motivated to participate in
 an open web. It is especially clear that while many of these platforms
 have been seeing some level of strategic neglect in favor of enhanced
 experiences at the price locking developers into their respective
 platforms. The Callback project exists to bring the focus back to an
 open and accessible web.
 
 Initial Goals
 -
 
 * License all PhoneGap source code and documentation to the Apache
 Software Foundation. (We already name the Apache license in our CLA.)
 * Setup and standardize the open governance of the Callback project.
 * Rename all assets from PhoneGap to Callback in project src, docs,
 tests and related infrastructure.
 
 Current Status
 --
 
 Callback is a mature software project recently shipping 1.0 on July 29, 2011.
 
 Meritocracy
 ---
 
 Callback has always been a project driven by merit and, in a sense, our
 solution is brute force requiring many collaborating developers to
 solve our goals.
 
 It would be far easier, and perhaps more correct, for the Callback
 project to port a single web browser codebase, and API bindings, across
 platforms but our executable size would be appreciably larger, unacceptably
 so for mobile, and our target abstraction would be only tertiary to
 maintaining a codebase of that size. By relying on the platform browser,
 exposed by the platform SDK, we get a quick win to the browser and only
 have to focus on our bridge. This means the project requires developers
 with proficiency on each platform: collaboration is a natural side effect.
 
 Community
 -
 
 The community surrounding Callback is vast, diverse, distributed globally,
 and with all levels of proficiency in software development---the 

Re: [VOTE] Graduation of the Chemistry Podling

[Felix Meschberger]

+1

Good luck !

Regards
Felix

Am Freitag, den 11.02.2011, 11:53 + schrieb Nick Burch: 
 Hi All
 
 The Chemistry podling has been in the incubator since early 2009. In the 
 last 6 months, the podling has had two sucessful Java releases, and now 
 its first sucessful non-Java release too. The community is healthy and 
 diverse, has added new committers, and brought in other code bases + their 
 communities via the IP clearing process.
 
 Following advice from the mentors, the Chemistry podling has now voted to 
 graduate:
 http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201102.mbox/%3calpine.deb.1.10.1102071443310.9...@urchin.earth.li%3E
 http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201102.mbox/%3calpine.deb.1.10.110230300.9...@urchin.earth.li%3E
 
 The vote has received 12 PPMC approvals, of which 2 were also IPMC 
 approvals (Jukka Zitting and myself).
 
 I'd therefore like to ask the IPMC to approve the graduation.
   +1 - I approve of the Chemistry graduation
0 - I've not had time to look into it, sorry
   -1 - There's an issue with graduation at this time, which is
 
 Voting will be open for 72 hours. Also, please find the proposed board 
 resolution below.
 
 Thanks
 Nick
 
 
 
 Establish the Apache Chemistry project
 
 WHEREAS, the Board of Directors deems it to be in the best interests
 of the Foundation and consistent with the Foundation's purpose to
 establish a Project Management Committee charged with the creation and
 maintenance of open-source software providing an implemention of the
 OASIS CMIS (Content Management Interoperability Services) specifications,
 in server and client form, for distribution at no charge to the public.
 
 NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
 (PMC), to be known as the Apache Chemistry Project, be and hereby is
 established pursuant to Bylaws of the Foundation; and be it further
 
 RESOLVED, that the Apache Chemistry Project be and hereby is responsible
 for the creation and maintenance of software providing and implementing
 the OASIS CMIS (Content Management Interoperability Services) specifications,
 in server and client form, for distribution at no charge to the public.
 
 RESOLVED, that the office of Vice President, Chemistry be and hereby is
 created, the person holding such office to serve at the direction of
 the Board of Directors as the chair of the Apache Chemistry Project, and
 to have primary responsibility for management of the projects within
 the scope of responsibility of the Apache Chemistry Project; and be it
 further
 
 RESOLVED, that the persons listed immediately below be and hereby are
 appointed to serve as the initial members of the Apache Chemistry Project:
 
 * Bogdan Stefanescu (b...@apache.org)
 * David Caruana (dcaru...@apache.org)
 * David Nuescheler  (unc...@apache.org)
 * David Ward(dw...@apache.org)
 * Dominique Pfister (dpfis...@apache.org)
 * Florent Guillaume (fguilla...@apache.org)
 * Florian Müller(f...@apache.org)
 * Gabriele Columbro (gabri...@apache.org)
 * Jeff Potts(jpo...@apache.org)
 * Jens Hübel(j...@apache.org)
 * Jukka Zitting (ju...@apache.org)
 * Martin Hermes (herm...@apache.org)
 * Nick Burch(n...@apache.org)
 * Paolo Mottadelli  (pa...@apache.org)
 * Paul Goetz(pgo...@apache.org)
 * Richard McKnight  (richa...@apache.org)
 * Stéfane Fermigier (sfermig...@apache.org)
 * Stephan Klevenz   (sklev...@apache.org)
 * Stéphane Lacoin   (slac...@apache.org)
 * Sun Seng David Tan(s...@apache.org)
 
 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Florian Müller be
 appointed to the office of Vice President, Chemistry, to serve in
 accordance with and subject to the direction of the Board of Directors
 and the Bylaws of the Foundation until death, resignation, retirement,
 removal or disqualification, or until a successor is appointed; and be
 it further
 
 RESOLVED, that the initial Apache Chemistry Project be and hereby is
 tasked with the creation of a set of bylaws intended to encourage open
 development and increased participation in the Chemistry Project; and be
 it further
 
 RESOLVED, that the initial Apache Chemistry Project be and hereby is
 tasked with the migration and rationalization of the Apache Incubator
 Chemistry podling; and be it further
 
 RESOLVED, that all responsibility pertaining to the Apache Incubator
 Chemistry podling encumbered upon the Apache Incubator PMC are hereafter
 discharged.
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: 

Re: [VOTE] Accept Stanbol for incubation

[Felix Meschberger]

+1

Regards
Felix

Am Mittwoch, den 10.11.2010, 16:11 +0100 schrieb Bertrand Delacretaz: 
 Hi,
 
 I think we're ready to vote on the
 http://wiki.apache.org/incubator/StanbolProposal now, copy included
 below.
 
 This is TPFKAF - The Project Formerly Known As FOO.
 
 Please cast your votes:
 
 [ ] +1 Accept Stanbol for incubation
 [ ] +0 Don't care
 [ ] -1 Reject for the following reason:
 
 The vote is open for at least 72 hours.
 
 Thanks!
 -Bertrand
 
 
 = Apache Stanbol incubation proposal =
 
 == Abstract ==
 Apache Stanbol is a modular software stack and reusable set of
 components for semantic content management.
 
 == Proposal ==
 Stanbol components are meant to be accessed over RESTful interfaces to
 provide semantic services for content management. The current code is
 written in Java and based on the OSGi modularization framework, but
 other server-side languages might be used as well.
 
 Applications include extending existing content management systems
 with (internal or external) semantic services, and creating new types
 of content management systems with semantics at their core.
 
 The architecture of the current (alpha-level) code consists of four layers:
  * Persistence: services that store (or cache) semantic information
 and make it searchable
  * Lifting: services that add semantic information to “non-semantic”
 pieces of content
  * Knowledge models and reasoning: services that enhance the semantic
 information
  * Interaction: intelligent user interface management and generation
 
 == Background ==
 Stanbol comes out of the IKS project (Interactive Knowledge Stack,
 http://iks-project.eu/), a research project funded by the European
 Community (EC) which aims to create a semantic content management
 software stack.
 
 One of the goals of IKS is for its software to survive the 4-year
 funding period of the EC, which ends in 2012.
 
 Developing its code in the open at the Apache Software Foundation, and
 growing a community before IKS funding runs out, is the best way to
 ensure the sustainability of the Stanbol software.
 
 For more background information, some articles and tutorials on FISE,
 which was the first usable IKS module, can be found in the “FISE
 links” section of http://wiki.iks-project.eu/index.php/FISE
 
 == Rationale ==
 Content Management Systems (CMS) can benefit from semantic add-ons in
 a number of ways, including more intelligent linking, automatic or
 semi-automatic tagging of content, enhanced user interactions based on
 intelligent and dynamically adaptable user scenario modeling, etc.
 
 However, many CMS vendors and developers are not aware of or skilled
 enough in semantic technologies to make effective use of them.
 Research in semantic technologies often happens in academic circles
 which might not make their findings available in a way that’s easily
 consumable by today’s CMS vendors and developers.
 
 Some big companies are using semantic technologies behind the scenes
 to provide powerful services, but that technology is usually not
 accessible to smaller vendors.
 
 Stanbol aims to bridge these gaps by providing CMS vendors and
 developers with easy to integrate semantic components that add value
 to their offerings.
 
 At the same time, more experimental advanced semantic applications
 will be built on the Stanbol stack, with the medium-term goal of
 enabling pure semantic-based content management and other
 applications.
 
 == Initial Goals ==
  * Import the existing IKS code.
  * Clean up as needed to take advantage of Apache infrastructure
 (Hudson continuous builds, etc.)
  * Replace up any dependencies that do not fulfill Apache licensing criteria.
  * Create the Stanbol website and migrate IKS website/wiki information
 to it as needed.
  * Make a first release and publicize it to start growing the community.
 
 == Current Status ==
 === Meritocracy ===
 As IKS is an EC research project with funding, it does not formally
 operate as a meritocracy.
 
 However, due to the open source way of working adopted by the
 consortium, an informal meritocracy has emerged within IKS.
 
 We estimate that adapting to the ASF’s meritocratic way of working
 will be easy for the initial set of Stanbol committers, as the
 differences to the current way of working are not dramatic.
 
 === Community ===
 The IKS project plan includes an important effort to build a community
 around the software that it produces. Several community workshops have
 already taken place, attended by more than 40 European CMS developers
 and vendors.
 
 See http://wiki.iks-project.eu/index.php/Workshops for more info.
 
 A community is emerging around IKS, and moving to the Apache project
 governance model should help grow it - also by reassuring community
 members that the software will continue to be available and
 maintainable once the IKS EC funding runs out.
 
 === Core Developers ===
 The IKS consortium consists of seven academic research groups and six
 “industrial partners”, 

Re: [PROPOSAL] Boot strapping Android projects @ Apache

[Felix Meschberger]

+1

Regards
Felix


Am Dienstag, den 09.11.2010, 10:13 -0500 schrieb Noel J. Bergman: 
 About a half dozen or so of us met up at ApacheCon after the lightning talks
 to talk briefly about Android @ the ASF.
 
 The proposal is to create an android-inter...@i.a.o (we also thought about
 @labs, but the general consenus seemed to be the Incubator due to some of
 the Labs' restrictions, which we think are good restrictions).
 
 We want to encourage others working on Android-related code to share
 experience and existence with their fellow Committers.  For example, did you
 know that Felix  Aries already work with Android?  What else does?  What
 else should?  Etc.
 
 In other words, we want to provide a gathering point for all of the people
 working in isolation -- to provide a meeting place for those intersted in
 expanding Android-based activity at the ASF.  It is not so much an umbrella
 as a vital nexus, and breeding ground for importing or creating projects,
 which would then stand on their own.
 
   --- Noel
 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Celix for incubation

[Felix Meschberger]

+1

Regards
Felix


Am Donnerstag, den 28.10.2010, 22:37 +0200 schrieb Karl Pauls: 
 +1
 
 regards,
 
 Karl
 
 On Thu, Oct 28, 2010 at 9:47 PM, Davanum Srinivas dava...@gmail.com wrote:
  +1
 
  -- dims
 
  Sent from my iPhone
 
  On Oct 28, 2010, at 3:47 PM, Richard S. Hall he...@ungoverned.org wrote:
 
  +1
 
  - richard
 
 
  On 10/28/10 15:42, Marcel Offermans wrote:
  After the initial discussions about Celix have finished, we now have 
  three mentors and would like to call a vote to accept Celix into the 
  Apache Incubator.
 
  The proposal is included below and can also be found at:
  http://wiki.apache.org/incubator/CelixProposal
 
  Please cast your votes:
 
  [ ] +1 Accept Celix for incubation
  [ ] +0 Don't care
  [ ] -1 Reject for the following reason:
 
  Greetings, Marcel
 
 
 
  Celix
 
  = Abstract =
  Celix is a OSGi like implementation in C with a distinct focus on 
  interoperability between Java-OSGi and Celix.
 
  = Proposal =
  Celix will be an implementation of the OSGi specification adapted to C. 
  It will follow the API as close as possible, but since the OSGi 
  specification is written primarily for Java, there will be differences 
  (Java is OO, C is procedural).
  An important aspect of the implementation is interoperability between 
  Java-OSGi and Celix. This interoperability is achieved by porting and 
  implementing the Remote Services specification in Celix. These Services 
  will be made available in separate bundles.
 
  = Background =
  In embedded/realtime situations software is mostly implemented in C. In 
  situations where interoperability and dynamics are important, a good 
  architecture and design principle is needed. OSGi provides such 
  middleware for Java based systems.
  To be able to have such dynamic environment implemented in C, a OSGi like 
  implementation is needed. Besides a dynamic environment, OSGi also makes 
  it easier to reuse parts of the system, reducing time needed to implement 
  and maintain software.
  The implementation started with the basics to make it possible to load 
  libraries dynamically, and steadily grown towards an implementation where 
  large parts of the OSGi framework API is implemented.
  The implementation of Celix is heavily based on Apache Felix (where 
  appropriate it is even a direct port of the Apache Felix code (Java) to 
  C).
  Since distributed systems are used more and more in services based 
  environments, a scalable and transparent solution is needed for remote 
  communication. The OSGi specification describes remote services, this 
  specification will be a part of the first release.
  Remote services also make it possible to communicate between Java-OSGi 
  and Celix. To achieve this interoperability, both Java and C 
  implementations of remote services for a common protocol are needed. For 
  local services JNI can be used, for remote services SOAP and/or REST can 
  be used. In the latter case, Apache CXF can be used to implement the 
  Remote Services API in Java.
 
  = Rationale =
  In embedded/realtime/distributed environments there is a need to be able 
  to create dynamic and maintainable software. Currently there are no off 
  the shelf middleware/frameworks for this. Celix tries to provide such a 
  framework.
  The choice to base the implementation on the OSGi specification makes it 
  possible for a developer to use Celix as well as Java OSGi implementation 
  without much differences and without a steep learning curve.
  The community and user driven platform created by Apache provides a great 
  base for middleware such as Celix. Also the fact that Celix is based on 
  Apache Felix, and Apache Felix is hosted by Apache, makes it a logical 
  choice to have Apache as home for this project.
 
  = Initial Goals =
  * Provide a basic implementation of the OSGi Framework API
  * Provide an implementation of Remote Services to be able to create 
  distributed systems (and Celix-  OSGi interoperability).
  * Build/Expand a community using/developing Celix
  * OSGi like implementation in C
  * Provide a module/component based software solution for embedded 
  Platforms
o Real-Time software
o Distributed systems
o Provide Services based solution
  * Investigate if Apache Portable Runtime can be used for platform 
  abstraction
 
  = Current Status =
  == Meritocracy ==
  Celix was created by Alexander Broekhuis. While he is no active 
  committer/participant of Apache projects, he has used Open Source and is 
  well known with it and how a meritocracy works. Currently there are 
  several other possible committers.
  To be able to create and maintain complex middleware (such as Celix) a 
  good structure is needed. A meritocracy following the rules and 
  traditions of the ASF is a good choice for Celix.
 
  == Community ==
  Currently the Celix community exists out of the core developers, and the 
  users integration Celix in an 

Stepping down as a Mentor to the Chemistry Poddling

[Felix Meschberger]

Hi all,

I do not find enough cycles to follow any discussions at all on the
Chemistry mailing list. So I have at the moment, honestly and sadly, no
full clue on what's going on.

Since with Nick Burch, Jukka Zitting, and Gianugo Rabellino we have
experienced and active mentors for the project I feel save stepping down.

I wish you good luck on your journey to graduation !

Noel, you might want to take note of this change in your next Incubator
report.

I have already removed myself from project roaster on the Incubator's
project page.

Regards
Felix

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] Felix UPNP Web Console Plugin

[Felix Meschberger]

Hi,

No reaction within 72 hours, so I assume lazy consensus.

Thanks for watching.

We will now continue integrating this code.

Regards
Felix

On 16.03.2010 08:59, Felix Meschberger wrote:
 Hi,
 
 The Apache Felix project has received a contribution of the UPNP Web
 Console Plugin
 
 * The code is attached to JIRA issue FELIX-2121 [1]
   (MD5 of attachment: 80390b4b3bed18b16e54ab5492f4b96d)
 
 * The IP Clearance form has been committed to the Incubator website. [2]
 
 * A vote has passed on the d...@felix mailing list [3]
 
 The clearance passes by lazy consensus if no -1 votes are cast within
 the next 72 hours.
 
 Thanks and Regards
 Felix
 
 [1] https://issues.apache.org/jira/browse/FELIX-2121
 [2] http://incubator.apache.org/ip-clearance/felix-httpservice.html
 [3] http://markmail.org/message/b24r4nw2hbrzh2it

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP CLEARANCE] Felix UPNP Web Console Plugin

[Felix Meschberger]

Hi,

The Apache Felix project has received a contribution of the UPNP Web
Console Plugin

* The code is attached to JIRA issue FELIX-2121 [1]
  (MD5 of attachment: 80390b4b3bed18b16e54ab5492f4b96d)

* The IP Clearance form has been committed to the Incubator website. [2]

* A vote has passed on the d...@felix mailing list [3]

The clearance passes by lazy consensus if no -1 votes are cast within
the next 72 hours.

Thanks and Regards
Felix

[1] https://issues.apache.org/jira/browse/FELIX-2121
[2] http://incubator.apache.org/ip-clearance/felix-httpservice.html
[3] http://markmail.org/message/b24r4nw2hbrzh2it

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Shindig as an Apache Top Level Project

[Felix Meschberger]

+1

Regards
Felix

On 14.01.2010 12:41, Vincent Siveton wrote:
 Hi,
 
 Thanks for the positive feedback on the proposal to graduate Shindig
 as a TLP [1].
 
 I would like to start an official vote to recommend the graduation of
 Apache Shindig as a Top Level Project to the Board.
 To that end I have prepared the resolution for the Board below to be
 presented for consideration at the upcoming Board meeting.
 
 Community graduation vote thread:
 http://shindig-dev.markmail.org/message/c47amdxjtntkjij5
 
 Please cast your vote:
 [ ] +1 to recommend Shindig's graduation
 [ ] 0 don't care
 [ ] -1 no, don't recommend yet, because ...
 
 The vote will be open for 72 hours.
 
 Cheers,
 
 Vincent
 
 [1] http://apache.markmail.org/message/qvpyymihv6gyh5a7
 
 --- Begin Proposed Board Resolution ---
 
 WHEREAS, the Board of Directors deems it to be in the best interests of the
 Foundation and consistent with the Foundation's purpose to establish a Project
 Management Committee, charged with the creation and maintenance of open-source
 software related to the implementation of an OpenSocial container and
 OpenSocial API specifications, for distribution at no charge to the public.
 
 NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to
 be known as the Apache Shindig PMC, is hereby established pursuant to Bylaws
 of the Foundation; and be it further
 
 RESOLVED, that the Apache Shindig Project be and hereby is responsible for the
 creation and maintenance of software related to the OpenSocial API
 specifications, based on software licensed to the Foundation; and be it 
 further
 
 RESOLVED, that the office of Vice President, Apache Shindig be and hereby
 is created, the person holding such office to serve at the direction of the
 Board of Directors as the chair of Apache Shindig, and to have primary
 responsibility for management of the projects within the scope of 
 responsibility
 of the Apache Shindig PMC; and be it further
 
 RESOLVED, that the persons listed immediately below be and hereby are 
 appointed
 to serve as the initial members of the Apache Shindig PMC:
 
 * Ian Boston (ieb at apache dot org)
 * Kevin Brown (etnu at apache dot org)
 * Chris Chabot(chabotc at apache dot org)
 * Chico Charlesworth (chico at apache dot org)
 * Cassie Doll (doll at apache dot org)
 * Evan Gilbert (evan at apache dot org)
 * John Hjelmstad (johnh at apache dot org)
 * Paul Lindner (lindner at apache dot org)
 * Daniel Peterson (dpeterson at apache dot org)
 * Louis Ryan (lryan at apache dot org)
 * Henning Schmiedehausen (henning at apache dot org)
 * Vincent Siveton (vsiveton at apache dot org)
 * Upayavira (upayavira at apache dot org)
 * Adam Winer (awiner at apache dot org)
 
 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Paul Lindner be appointed to the
 office of Vice President, Apache Shindig, to serve in accordance with and
 subject to the direction of the Board of Directors and the Bylaws of the
 Foundation until death, resignation, retirement, removal or disqualification, 
 or
 until a successor is appointed; and be it further
 
 RESOLVED, that Apache Shindig be and hereby is tasked with the migration
 and rationalization of the Apache Incubator Shindig podling; and be it
 further
 
 RESOLVED, that all responsibilities pertaining to the Apache Incubator
 Shindig podling encumbered upon the Apache Incubator PMC are hereafter
 discharged.
 
 --- End Proposed Board Resolution ---
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)

[Felix Meschberger]

Hi,

Gianugo Rabellino schrieb:
 ... snip ...
 I wish this discussion happened on chemistry-dev, and I would actually
 like to see what the community as a whole thinks about it. I'd
 actually prefer to see OpenCMIS possibly spinning off from Chemistry
 after an unsuccessful integration attempt rather than merging at a
 later time.

I share Gianugo's and Bertrand's concerns. And as a mentor to the
Chemistry poddling, I am even somewhat more concerned

As such, I would welcome such discussion very much to take place and to
sort out the issues.

Regards
Felix


 
 And there are other Apache products co-existing in parallel (e.g. Axis and 
 CXF, just to pick one example), and the ASF has never stated that this has 
 to be avoided. So to me, it seemed that the idea of having two projects in 
 parallel isn't that bad.
 
 Oh, there are plenty, and duplication isn't inherently bad. The
 difference here (and it's a big one in my book) is that we are talking
 about two different podlings, with all the related issues of
 incubating projects such as finite resources and whatnot. And the fact
 they both aim to implement an unfinished spec doesn't quite help.
 
 May I suggest we move this discussion to the Chemistry lists in order
 to seek consensus over there? That would allow you to return to the
 Incubator with a proposal  properly addressing the duplication issue.
 If there is a thorough discussion over there, and a general agreement
 (including agreeing to disagree), I'll be happy to sign up as a
 mentor/champion for OpenCMIS.
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL][VOTE] Subversion

[Felix Meschberger]

+1

Regards
Felix

Greg Stein schrieb:
  Subversion is a version control system.  You probably know it well as
 it is the version control system employed by the Apache Software
 Foundation.
 
  The Subversion project would like to join the Apache Software
 Foundation to remove the overhead of having to run its own
 corporation.  The Subversion project is already run quite like an
 Apache project, and already counts a number of ASF Members amongst
 its committers.
 
  Work on Subversion was originally started at CollabNet; Karl Fogel
 was hired in January 2000.  Jim Blandy, at RedHat, already had an
 initial design for the storage system, which was incorporated into the
 FS design.  In February Brian Behlendorf invited Greg Stein to
 contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
 was hired in April 2000 to work on the project.  In that same month
 the first all hands meeting was held, where a number of interested
 people came together to talk about the project.
 
  Subversion was run as an open source project since the early days.
 Now, more than nine years later, it retains a healthy community,
 and has a good number of committers.  In the life span of Subversion,
 several committers have switched employers and have maintained involvement.
 The committership is diverse, both geographically as well as in terms of
 employment.
 
  The equivalent of the PMC consists of all the full committers to the
 Subversion project (currently around 55 people).  The community uses the
 voting process also used at the ASF.  Releases are signed off by gathering
 votes/digital signatures of each committer who verified the release
 candidate.
 
  We feel the ASF and Subversion communities are very compatible,
 witness the cross interest that already exists. There is both a
 vibrant developer as well as a large and active user community.
 Technology-wise, Subversion builds on APR, and implements two Apache
 HTTP Server modules.
 
  Note that Subversion has a number of related projects, which are not
 part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
 
  More information on Subversion can be found at
 http://www.subversion.org/ and http://subversion.tigris.org/.
 
  The Subversion Corporation has a license to all source code, and has
 CLAs on file for nearly all it's committers.  That is, we have all but
 one or two full committers, and some percentage of partial committers.
 
  We have a number of *user-configurable* dependencies which are not
 compatible with the AL:
  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
(An alternative HTTP client library, libsvn_ra_serf uses the Serf
 library under ALv2.)
 
  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
 is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
 under Academic Free License 2.1 or =GPL-2.
(This support is for integration for KDE and GNOME's authentication
 providers.)
 
  - libintl
(This library provides translation support for systems without
 a proper internationalization library.)
 
  - BDB
(This is used by the libsvn_fs_base system which stores its data
 in BDB; an alternative repository system called fs_fs does not
 have this dependency.)
 
 ---
 Required Resources
  - Mailing lists
- dev
- issues
- users
- private
- commits
- announce
- breakage (see
 http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
- We will work with the Infrastructure team to transfer the subscriber
  listings to the new destinations.
  - Subversion:
- We have not made a decision whether we prefer Subversion should be
  imported into the main ASF Subversion repository or be hosted as a
  separate repository to enable early testing of the repository code.  We
  intend to discuss this during the Incubation process before the code is
  imported.  It is also understood that ASF infrastructure team may be
  willing to run custom pre-release Subversion server builds for the
  entire ASF, so this separate repository option may not be required.
- The Subversion source code can be found at:
  http://svn.collab.net/repos/svn/.
  - Issue tracking
- We haven't made a decision between JIRA or Bugzilla at this time and
  expect this decision to be made as part of the Incubation process.  Our
  current issue tracking system uses Issuezilla (a fork of Bugzilla) and
  we have not yet decided whether we want to import our previous issues
  into the new system and will decide this in the course of the Incubation
  process.
- Our current issue tracker is at
  http://subversion.tigris.org/issue-tracker.html.
  - Buildbot
- We currently use buildbot across a number of platforms and configurations
  for automated builds and testing.  Over time, we would like to migrate
  these services to Apache infrastructure where appropriate.
- Our current buildbot 

Re: [IP CLEARANCE] Apache Felix Improved Http Service

[Felix Meschberger]

Hi,

Richard S. Hall schrieb:
 We need the software grant on file for this, did I miss it?

The grant has been recorded and I have updated the IP-Clearance page [2]

Regards
Felix

 
 - richard
 
 On 9/4/09 7:25, Felix Meschberger wrote:
 Hi,

 The Apache Felix project has received a contribution of an Improved OSGi
   HttpService implementation

 * The code is attached to the FELIX-1456 JIRA issue [1]

 * The IP Clearance form has been committed to the Incubator website. [2]

 * A vote has passed on the d...@felix mailing list [3]

 The clearance passes by lazy consensus if no -1 votes are cast within
 the next 72 hours.

 Thanks and Regards
 Felix

 [1] https://issues.apache.org/jira/browse/FELIX-1456
 [2] http://incubator.apache.org/ip-clearance/felix-httpservice.html
 [3] http://www.mail-archive.com/d...@felix.apache.org/msg11895.html


 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[IP CLEARANCE] Apache Felix Improved Http Service

[Felix Meschberger]

Hi,

The Apache Felix project has received a contribution of an Improved OSGi
 HttpService implementation

* The code is attached to the FELIX-1456 JIRA issue [1]

* The IP Clearance form has been committed to the Incubator website. [2]

* A vote has passed on the d...@felix mailing list [3]

The clearance passes by lazy consensus if no -1 votes are cast within
the next 72 hours.

Thanks and Regards
Felix

[1] https://issues.apache.org/jira/browse/FELIX-1456
[2] http://incubator.apache.org/ip-clearance/felix-httpservice.html
[3] http://www.mail-archive.com/d...@felix.apache.org/msg11895.html


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Chemistry, Kato, Wink initial steps

[Felix Meschberger]

Hi,

David Crossley schrieb:
 Would the projects Chemistry, Kato, and Wink
 please add themselves to the main Currently in incubation table:
 [1] http://incubator.apache.org/projects/

Done for Chemistry.

Thanks for reminding.

Regards
Felix

 
 See how to notes via links from the Steps section at
 [2] http://incubator.apache.org/clutch.html#h-Sponsor
 
 That table [1] and the Wiki ReportingSchedule [3]
 [3] http://wiki.apache.org/incubator/ReportingSchedule
 are the main pages that enable the Incubator to know what
 projects are on our radar.
 
 Also if those two simple resources are missing, then
 Clutch cannot properly assist.
 
 Any project committer can do these edits.
 
 -David
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduation for Sanselan

[Felix Meschberger]

+1

Regards
Felix

Craig L Russell schrieb:
 Hi,
 
 Sanselan has been in incubation since September 2007. Sanselan is a
 pure-java image library for reading and writing a variety of image formats.
 
 Monthly and then quarterly reports can be found at
 http://svn.apache.org/repos/asf/incubator/sanselan/board/
 The first official Apache Sanselan incubating release occurred on July
 30th, 2008.
 A few months back we took a final look at Sanselan's status with regard
 to exiting the incubator. We concluded that while the code and the
 committer for Sanselan were ready to exit the incubator, community was
 an issue. We didn't see the prospect for getting enough of a community
 to graduate Sanselan as a TLP. But Apache Commons was eager to adopt
 Sanselan, and they voted to do so.
 Sanselan is now ready to graduate the incubator and assume its role as a
 subproject of Apache Commons.
 Please review the checklist at
 http://incubator.apache.org/projects/sanselan.html and verify that
 Sanselan is ready.
 
 +1 graduate Sanselan into Apache Commons
 +-0 don't care
 -1 don't graduate because...
 
 Voting will remain open until Thursday June 25.
 
 Craig L Russell
 Incubator PMC, DB PMC, OpenJPA PMC
 c...@apache.org http://db.apache.org/jdo
 
 
 
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Graduate Apache Sling as Top Level Project

[Felix Meschberger]

Hi,

The voting period has passed by and we received the following votes
(votes marked with * are binding):

  +1 Felix Meschberger (*)
  +1 Betrand Delacretaz (*)
  +1 Davanum Srinivas (*)
  +1 Niklas Gustavsson
  +1 Luciano Rensende (*)
  +1 Jeremias Maerki (*)
  +1 Carsten Ziegeler (*)
  +1 Niklas Hedhman (*)
  +1 Martijn Dashorst (*)
  +1 Craig L. Russell (*)
  +1 Jukka Zitting (*)
  +1 Daniel Kulp (*)
  +1 Stefan Bodewig (*)

This vote therefore passes with 13 +1 votes (12 of which binding). No
other votes were cast.

Also there were no remarks regarding the board resolution draft. So I
consider this draft ready for submission to the board.

Besides thanking you all for your votes I would like to thank you for
your wishes and nice words. This is appreciated.

Regards
Felix

Felix Meschberger schrieb:
 Hi all,
 
 Thanks for the positive feedback on the proposal to graduate Sling as a
 Top Level Project [1]. Based on this feedback, I would like to launch
 the vote to recommend the graduation of Apache Sling as a Top Level
 Project to the Board.
 
 
 So please cast your votes:
 
   [ ] +1 to recommend Sling's graduation
   [ ]  0 don't care
   [ ] -1 no, don't recommend yet, because ...
 
 
 Due to a public holiday on monday in many locations and the weekend,
 this vote will be open for 5 days (until Thursday, June 4th 2009).
 
 For reference I also attach the board resolution draft.
 
 Thanks for your votes.
 
 Regards
 Felix
 
 
 References:
 
 Gradiation proposal thread on Incubator General [1]
   http://markmail.org/thread/gxazyfua2xpdztdi
 
 Vote thread on Sling Dev List
   http://markmail.org/message/76yu7qatqfqnrdme
 
 Graduation vote result on Sling Dev List
   http://markmail.org/message/7kxbtj7tdjr4jezw
 
 
 
 Board Resolution Draft
 
 
 X. Establish the Apache Sling Project
 
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software related to a scriptable web framework
that uses a Java Content Repository, such as Apache
Jackrabbit, to store and manage content for distribution
at no charge to the public.
 
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Sling PMC,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
 
RESOLVED, that the Apache Sling Project be and hereby is
responsible for the creation and maintenance of software
related to a scriptable web framework that uses a Java
Content Repository, such as Apache Jackrabbit, to store
and manage content; and be it further
 
RESOLVED, that the office of Vice President, Apache Sling be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Sling Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Sling Project; and be it further
 
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Sling Project:
 
  * Alexandru Popescu  apopescu at apache dot org
   * Bertrand Delacretazbdelacretaz at apache dot org
   * Christophe Lombart clombart at apache dot org
   * Carsten Ziegeler   cziegeler at apache dot org
   * Felix Meschberger  fmeschbe at apache dot org
   * Gianugo Rabellino  gianugo at apache dot org
   * Padraic Hannon hannonpi at apache dot org
   * Juan José Vázquez Delgado  juanjo at apache dot org
   * Karl Pauls pauls at apache dot org
   * Vidar Ramdal   vramdal at apache dot org
 
 
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Felix Meschberger
be appointed to the office of Vice President, Apache Sling, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
 
RESOLVED, that the initial Apache Sling PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Sling Project; and be it further
 
RESOLVED, that the Apache Sling Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Sling podling; and be it further
 
RESOLVED, that all responsibilities pertaining to the Apache

[RESULT] [VOTE] Approve Release of Apache Sling MIME type mapping support Version 2.1.0-incubator

[Felix Meschberger]

Hi all,

Time to tally this vote.

Besides the votes already cast by IPMC members Felix Meschberger, 
Carsten Ziegeler, Bertrand Delacretaz, and Jukka Zitting we got another 
+1 vote from Niclas Hedhman.


Thus this vote passes with 5 +1 votes. No other votes have been cast.

Since the JavaDoc package does not meet the release requirements, it 
will not be published to the maven repository.


Regards
Felix

Felix Meschberger schrieb:

The Apache Sling community voted on and has approved a proposal to
release Apache Sling MIME type mapping support Version 2.1.0-incubator
bundle. Pursuant to the Releases section of the Incubation Policy we
would now like to request the permission of the Incubator PMC to publish
the tarball on the Sling Download page (this will be
http://incubator.apache.org/sling/site/download.html).

The following votes were cast:

  +1 Felix Meschberger
  +1 Carsten Ziegeler
  +1 Bertrand Delacretaz
  +1 Jukka Zitting

This vote therefore passed with 4 +1 votes and no other votes. All
voters are members of the Sling PPMC and the Incubator PMC.

Please cast your votes!

Thanks
Felix


Proposal, vote thread and vote result:
http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200905.mbox/%3c4a1130b0.3030...@gmail.com%3e

Releases section of the Incubation Policy:
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases





-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Graduate Apache Sling as Top Level Project

[Felix Meschberger]

Hi all,

Thanks for the positive feedback on the proposal to graduate Sling as a 
Top Level Project [1]. Based on this feedback, I would like to launch 
the vote to recommend the graduation of Apache Sling as a Top Level 
Project to the Board.



So please cast your votes:

  [ ] +1 to recommend Sling's graduation
  [ ]  0 don't care
  [ ] -1 no, don't recommend yet, because ...


Due to a public holiday on monday in many locations and the weekend, 
this vote will be open for 5 days (until Thursday, June 4th 2009).


For reference I also attach the board resolution draft.

Thanks for your votes.

Regards
Felix


References:

Gradiation proposal thread on Incubator General [1]
  http://markmail.org/thread/gxazyfua2xpdztdi

Vote thread on Sling Dev List
  http://markmail.org/message/76yu7qatqfqnrdme

Graduation vote result on Sling Dev List
  http://markmail.org/message/7kxbtj7tdjr4jezw



Board Resolution Draft


X. Establish the Apache Sling Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software related to a scriptable web framework
   that uses a Java Content Repository, such as Apache
   Jackrabbit, to store and manage content for distribution
   at no charge to the public.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Sling PMC,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Sling Project be and hereby is
   responsible for the creation and maintenance of software
   related to a scriptable web framework that uses a Java
   Content Repository, such as Apache Jackrabbit, to store
   and manage content; and be it further

   RESOLVED, that the office of Vice President, Apache Sling be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache Sling Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Sling Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache Sling Project:

 * Alexandru Popescu  apopescu at apache dot org
 * Bertrand Delacretazbdelacretaz at apache dot org
 * Christophe Lombart clombart at apache dot org
 * Carsten Ziegeler   cziegeler at apache dot org
 * Felix Meschberger  fmeschbe at apache dot org
 * Gianugo Rabellino  gianugo at apache dot org
 * Padraic Hannon hannonpi at apache dot org
 * Juan José Vázquez Delgado  juanjo at apache dot org
 * Karl Pauls pauls at apache dot org
 * Vidar Ramdal   vramdal at apache dot org


   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Felix Meschberger
   be appointed to the office of Vice President, Apache Sling, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the initial Apache Sling PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Sling Project; and be it further

   RESOLVED, that the Apache Sling Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Sling podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Sling podling encumbered upon the Apache Incubator
   Project are hereafter discharged.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Sling as Top Level Project

[Felix Meschberger]

+1, of course ;-)

Regards
Felix


Felix Meschberger schrieb:

Hi all,

Thanks for the positive feedback on the proposal to graduate Sling as a 
Top Level Project [1]. Based on this feedback, I would like to launch 
the vote to recommend the graduation of Apache Sling as a Top Level 
Project to the Board.



So please cast your votes:

  [ ] +1 to recommend Sling's graduation
  [ ]  0 don't care
  [ ] -1 no, don't recommend yet, because ...


Due to a public holiday on monday in many locations and the weekend, 
this vote will be open for 5 days (until Thursday, June 4th 2009).


For reference I also attach the board resolution draft.

Thanks for your votes.

Regards
Felix


References:

Gradiation proposal thread on Incubator General [1]
  http://markmail.org/thread/gxazyfua2xpdztdi

Vote thread on Sling Dev List
  http://markmail.org/message/76yu7qatqfqnrdme

Graduation vote result on Sling Dev List
  http://markmail.org/message/7kxbtj7tdjr4jezw



Board Resolution Draft


X. Establish the Apache Sling Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software related to a scriptable web framework
   that uses a Java Content Repository, such as Apache
   Jackrabbit, to store and manage content for distribution
   at no charge to the public.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Sling PMC,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Sling Project be and hereby is
   responsible for the creation and maintenance of software
   related to a scriptable web framework that uses a Java
   Content Repository, such as Apache Jackrabbit, to store
   and manage content; and be it further

   RESOLVED, that the office of Vice President, Apache Sling be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache Sling Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Sling Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache Sling Project:

 * Alexandru Popescu  apopescu at apache dot org
  * Bertrand Delacretazbdelacretaz at apache dot org
  * Christophe Lombart clombart at apache dot org
  * Carsten Ziegeler   cziegeler at apache dot org
  * Felix Meschberger  fmeschbe at apache dot org
  * Gianugo Rabellino  gianugo at apache dot org
  * Padraic Hannon hannonpi at apache dot org
  * Juan José Vázquez Delgado  juanjo at apache dot org
  * Karl Pauls pauls at apache dot org
  * Vidar Ramdal   vramdal at apache dot org


   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Felix Meschberger
   be appointed to the office of Vice President, Apache Sling, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the initial Apache Sling PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache Sling Project; and be it further

   RESOLVED, that the Apache Sling Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Sling podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Sling podling encumbered upon the Apache Incubator
   Project are hereafter discharged.





-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Approve Release of Apache Sling MIME type mapping support Version 2.1.0-incubator

[Felix Meschberger]

Hi Sebb,

sebb schrieb:

The signing key for 0xF79B7715 is not in the KEYS file:

http://svn.apache.org/repos/asf/incubator/sling/trunk/KEYS

This must be fixed before release.


Hmm, I added it to

   http://www.apache.org/dist/incubator/sling/KEYS

But I now also added it to the sling/trunk/KEYS file


http://svn.apache.org/repos/asf/incubator/sling/tags/org.apache.sling.commons.mime-2.1.0-incubator/

If so, then this agrees with the tgz and source archives, except for
line-endings.

It would be helpful if the NOTICE file mentioned JQuery TreeTable, e.g.

This product includes JQuery TreeTable software developed by

This can be fixed in the next release.


makes sense. done (for the next release)



Maven reports the following problem:

[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, i.e. build is platform dependent!

The encoding needs to be explicitly defined if the pom uses filtering.


We do not use filtering for now, so this is not an issue.



It would be useful if the Manifest files in the jars contained the
Specification and Implementation entries.


We have the OSGi manifest headers, mostly the Bundle-SymbolicName, 
Bundle-Version and Bundle-Name headers. These are equivalent. But we 
will certainly consider adding at least the Implementation entries in 
future releases.




The Javadoc jar does not contain a NOTICE or a LICENSE file (nor is
the disclaimer mentioned)

I think this needs to be fixed before release.


Hmm, too bad. So lets not publish the Javadoc packages and go on with 
the release.




==

There are various missing SVN properties in


Hmm, thanks for remarking ... Will have to recheck my svn config file 
again ... (I thought I did that already ;-)


Regards
Felix



On 25/05/2009, Niclas Hedhman nic...@hedhman.org wrote:

+1


 On May 25, 2009 6:05 PM, Felix Meschberger fmesc...@gmail.com wrote:

 The Apache Sling community voted on and has approved a proposal to
 release Apache Sling MIME type mapping support Version 2.1.0-incubator
 bundle. Pursuant to the Releases section of the Incubation Policy we
 would now like to request the permission of the Incubator PMC to publish
 the tarball on the Sling Download page (this will be
 http://incubator.apache.org/sling/site/download.html).

 The following votes were cast:

  +1 Felix Meschberger
  +1 Carsten Ziegeler
  +1 Bertrand Delacretaz
  +1 Jukka Zitting

 This vote therefore passed with 4 +1 votes and no other votes. All
 voters are members of the Sling PPMC and the Incubator PMC.

 Please cast your votes!

 Thanks
 Felix


 Proposal, vote thread and vote result:
 
http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200905.mbox/%3c4a1130b0.3030...@gmail.com%3e

 Releases section of the Incubation Policy:
 http://incubator.apache.org/incubation/Incubation_Policy.html#Releases



 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Approve Release of Apache Sling MIME type mapping support Version 2.1.0-incubator

[Felix Meschberger]

Hi,

sebb schrieb:

On 27/05/2009, Felix Meschberger fmesc...@gmail.com wrote:

Maven reports the following problem:

[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, i.e. build is platform dependent!

The encoding needs to be explicitly defined if the pom uses filtering.


 We do not use filtering for now, so this is not an issue.



You may not have used filters explicitly, but the Maven message says
that it is using Cp1252, so clearly the encoding IS an issue.


Right. And I agree, that we will setup the resource plugin to force 
UTF-8 for future builds (we are currently voting on using repository.a.o 
for deployments and as a consequence would the inherit vom Apache parent 
6, which IIRC has the resource plugin setup correct).





It would be useful if the Manifest files in the jars contained the
Specification and Implementation entries.


 We have the OSGi manifest headers, mostly the Bundle-SymbolicName,
Bundle-Version and Bundle-Name headers. These are equivalent. But we will
certainly consider adding at least the Implementation entries in future
releases.


I am referring to items such as:

Implementation-Title:
Implementation-Vendor:
Implementation-Vendor-Id:
Implementation-Version:
Specification-Title:
Specification-Vendor:
Specification-Version:

Although some of the values are present in Bundle headers, the above
are more standard for non-OSGI applications.


Ok. We will setup the bundle plugin to include these standard headers.

Regards
Felix




The Javadoc jar does not contain a NOTICE or a LICENSE file (nor is
the disclaimer mentioned)

I think this needs to be fixed before release.


 Hmm, too bad. So lets not publish the Javadoc packages and go on with the
release.



OK.


==

There are various missing SVN properties in


 Hmm, thanks for remarking ... Will have to recheck my svn config file again
... (I thought I did that already ;-)

 Regards
 Felix




On 25/05/2009, Niclas Hedhman nic...@hedhman.org wrote:


+1


 On May 25, 2009 6:05 PM, Felix Meschberger fmesc...@gmail.com

wrote:

 The Apache Sling community voted on and has approved a proposal to
 release Apache Sling MIME type mapping support Version 2.1.0-incubator
 bundle. Pursuant to the Releases section of the Incubation Policy we
 would now like to request the permission of the Incubator PMC to

publish

 the tarball on the Sling Download page (this will be
 http://incubator.apache.org/sling/site/download.html).

 The following votes were cast:

 +1 Felix Meschberger
 +1 Carsten Ziegeler
 +1 Bertrand Delacretaz
 +1 Jukka Zitting

 This vote therefore passed with 4 +1 votes and no other votes. All
 voters are members of the Sling PPMC and the Incubator PMC.

 Please cast your votes!

 Thanks
 Felix


 Proposal, vote thread and vote result:


http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200905.mbox/%3c4a1130b0.3030...@gmail.com%3e

 Releases section of the Incubation Policy:


http://incubator.apache.org/incubation/Incubation_Policy.html#Releases





-

 To unsubscribe, e-mail:

general-unsubscr...@incubator.apache.org

 For additional commands, e-mail:

general-h...@incubator.apache.org





-

To unsubscribe, e-mail:

general-unsubscr...@incubator.apache.org

For additional commands, e-mail:

general-h...@incubator.apache.org




-
 To unsubscribe, e-mail:
general-unsubscr...@incubator.apache.org
 For additional commands, e-mail:
general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[PROPOSAL] Graduate Apache Sling as Top Level Project

[Felix Meschberger]

Hi all,

The Sling podling has voted on asking the Incubator PMC to support its
graduation as a top level project.

The vote passed with 23 +1 votes (8 of which from PPMC members), no 0
and no -1 votes. The vote thread can be found at [1], the result at [2].

Sling has been in the Incubator since September 5th, 2007. During its
incubation, Sling has ...

 * produced two releases
 * added two committers/PPMC members
 * added a documentation committer
 * received numerous contributions

Finally, let me quote our Champion Jukka Zitting:

  mentor hat on
  Day employees are still behind the majority of Sling
  commits, but the project has shown ability to welcome
  new ideas and contributors and to include them as
  equal members in the development and decision making
  processes. Also the other graduation criteria have been
  met and I don't think there's anything more that the
  Incubator can give to Sling.

  Thanks to everyone who's been participating so far,
  and good luck to Apache Sling as a standalone TLP!
  /mentor hat on

We have prepared the board resolution on our wiki at [3].

Regards
Felix


[1] http://markmail.org/message/76yu7qatqfqnrdme
[2] http://www.mail-archive.com/sling-...@incubator.apache.org/msg10305.html
[3] http://cwiki.apache.org/SLING/graduation-resolution-draft.html

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Approve Release of Apache Sling MIME type mapping support Version 2.1.0-incubator

[Felix Meschberger]

The Apache Sling community voted on and has approved a proposal to
release Apache Sling MIME type mapping support Version 2.1.0-incubator
bundle. Pursuant to the Releases section of the Incubation Policy we
would now like to request the permission of the Incubator PMC to publish
the tarball on the Sling Download page (this will be
http://incubator.apache.org/sling/site/download.html).

The following votes were cast:

  +1 Felix Meschberger
  +1 Carsten Ziegeler
  +1 Bertrand Delacretaz
  +1 Jukka Zitting

This vote therefore passed with 4 +1 votes and no other votes. All
voters are members of the Sling PPMC and the Incubator PMC.

Please cast your votes!

Thanks
Felix


Proposal, vote thread and vote result:
http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200905.mbox/%3c4a1130b0.3030...@gmail.com%3e

Releases section of the Incubation Policy:
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[INFO] Graduation Vote started

[Felix Meschberger]

Hi all,

The Apache Sling poddling has started a vote on proposing graduation as
a top level project to the Incubator PMC.

The vote thread is at [1].

Regards
Felix

[1] http://markmail.org/message/76yu7qatqfqnrdme

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Apache Ace into the Incubator

[Felix Meschberger]

 projects to make that happen. For building
 and testing we use Apache Ant and have developed a couple of
 extensions that help managing OSGi projects. Finally, at least
 informally a couple of projects at Apache have already expressed
 interest in a system that can help them do software provisioning.
 
 
 Known Risks
 
 Apache Ace uses Felix as its default OSGi implementation and some of
 its developers are also part of the Felix community. We are open to
 collaborate with other Apache projects, looking at candidates such as
 Commons, Sling, JackRabbit that could help us in certain parts of our
 infrastructure.
 
 An important reason for open sourcing this project at Apache is the
 strong community, as well as the Apache license. This will attract
 more users and developers so the project can be moved forward into new
 directions that we would otherwise not have been possible. Judging
 from the initial interest from some of the other projects at Apache,
 we certainly see ways in which to collaborate and advance the project,
 possibly in ways we would never have thought of. However, we have been
 able to support and develop this product outside of Apache quite well,
 so in no way are we trying to just dump the code there or merely
 trying to generate publicity.
 
 
 Initial Source
 
 Apache Ace has been in development within luminis since 2005.
 
 
 Source and Intellectual Property Submission Plan
 
 The current codebase is owned by luminis, and will be donated together
 with its documentation. We will get the paperwork out of the way as
 soon as possible. There should already be a CCLA on file for luminis
 and the people that are already involved with Apache obviously have
 ICLAs on file.
 
 
 External Dependencies
 
 There are quite a few open source libraries already used. The
 libraries, their sources and licenses are listed here:
 
 Apache Felix, ASL:
 * framework
 * shell
 * shell-tui
 * obr
 * http.jetty
 * config admin
 * event admin
 * deployment admin
 * dependency manager
 * prefs
 * upnp.basedriver
 * org.osgi.foundation
 * core
 * compendium
 * javax.servlet
 
 Apache Ant, ASL:
 * ant.jar
 * ant-contrib.jar
 
 Apache Velocity, ASL:
 * velocity
 
 KXML2 ( http://kxml.sourceforge.net/kxml2/), BSD license:
 * kxml2 (hmm, what was that issue we had with that in felix)
 
 Knopflerfish ( http://knopflerfish.org/), BSD style license:
 * log_all.jar, useradmin_all.jar
 
 Luminis Open Source Server ( https://opensource.luminis.net/), BSD license:
 * net.luminis.build.plugin.jar
 
 XStream ( http://xstream.codehaus.org/), BSD license:
 * various xstream jars
 
 
 Required Resources
 
 Mailing lists:
 * ace-private
 * ace-dev
 * ace-commits
 * ace-user (only after leaving the incubator)
 
 Subversion:
 * https://svn.apache.org/repos/asf/incubator/ace
 
 Issue Tracking:
 * JIRA: Apache Ace (ACE)
 
 Wiki:
 * Confluence: Apache Ace (ACE)
 
 
 Initial Committers
 
 These existing Apache committers have either worked on the initial
 codebase (Christian, Karl and Marcel) or expressed an interest in
 extending the project:
 * Marcel Offermans
 * Karl Pauls
 * Christian van Spaandonk
 * Clement Escoffier
 * Felix Meschberger
 * Carsten Ziegeler
 
 
 Community Members
 
 The following people have already expressed their interest in actively
 participating in this project:
 * Bram de Kruijff
 * Toni Menzel
 * Alin Dreghiciu
 * Dennis Geurts
 
 
 Affiliations
 
 For the record, Marcel Offermans, Christian van Spaandonk and Dennis
 Geurts work at luminis and might get paid to do certain work on Apache
 Ace.
 
 
 Sponsors
 
 We have approached both the champion and an initial list of mentors
 that have agreed to mentor this project.
 
 Champion:
 * Karl Pauls
 
 Mentors:
 * Carsten Ziegeler
 * Niclas Hedhman
 * Bertrand Delacretaz
 
 Sponsor:
 * Apache Incubator
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: PPMC Member list

[Felix Meschberger]

Hi,

Bertrand Delacretaz schrieb:
 On Fri, Apr 17, 2009 at 10:36 PM, Janne Jalkanen
 janne.jalka...@ecyrd.com wrote:
 ...Voting a new PPMC member guide at
 http://incubator.apache.org/guides/ppmc.html#Voting+in+a+new+PPMC+member says
 that new PPMC members should be added to
 https://svn.apache.org/repos/private/committers/board/incubator-info.txt.
 However, neither I nor the project mentors seem to be able to find the file.

 Any clues as to what to do next?...
 
 I don't remember adding PPMC members to such a file in the podlings
 that I've been mentoring - my guess would be that we just stopped
 maintaining that file.
 
 Can anyone confirm?

AFAICT we udpdate the poddling status page with the PPMC members.

Regards
Felix

 
 -Bertrand
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: PPMC Member list

[Felix Meschberger]

Hi Janne,

Janne Jalkanen schrieb:
 
 I don't remember adding PPMC members to such a file in the podlings
 that I've been mentoring - my guess would be that we just stopped
 maintaining that file.

 Can anyone confirm?

 AFAICT we udpdate the poddling status page with the PPMC members.
 
 Should I file a JIRA issue to get it fixed from the website?
 
 BTW, how do new PPMC members get added to the project-private -mailing
 lists? That info is missing from the guide too.

This is described at [1] and you should have enough karma to do this.

Regards
Felix

[1]
http://incubator.apache.org/guides/website.html#Edit+your+project+status+report

 
 /Janne
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: New Incubator Proposal: Null - A cloud-aware Web 3.0 Container

[Felix Meschberger]

Hi,

Upayavira schrieb:
 On Wed, 2009-04-01 at 07:23 +0200, Felix Meschberger wrote:
 Hi,

 together with Bertrand Delacretaz, Carsten Ziegeler, and Jukka Zitting,
 I came up with a proposal to bring our cloud-aware Web 3.0 Container to
 Apache.

 You'll find all the details here:

http://wiki.apache.org/incubator/NullProposal

 Now, currently we are looking for interested parties. So if you are
 interested in this proposal, please add your name to the wiki page.

 If anything is missing/unclear etc. let's discuss it :)
 
 My wholehearted +1. I'll mentor it.

Great. Thanks.

So this should releave Gavin's concerns quite a bit.

 This could be the next big thing at
 Apache after:
 
 http://markmail.org/message/iz6ejtre3dwtfgdo

Cool stuff!

Regards
Felix

 
 Upayavira
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

New Incubator Proposal: Null - A cloud-aware Web 3.0 Container

[Felix Meschberger]

Hi,

together with Bertrand Delacretaz, Carsten Ziegeler, and Jukka Zitting,
I came up with a proposal to bring our cloud-aware Web 3.0 Container to
Apache.

You'll find all the details here:

   http://wiki.apache.org/incubator/NullProposal

Now, currently we are looking for interested parties. So if you are
interested in this proposal, please add your name to the wiki page.

If anything is missing/unclear etc. let's discuss it :)

Regards
Felix
fmeschbe(at)apache(dot)org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Some advice needed on JSPWiki package names

[Felix Meschberger]

Hi all,

Noel J. Bergman schrieb:
 Janne,
 
 You and I had the same thought.  I suggest going with org.apache.JSPWiki, as
 suggested by you in
 https://issues.apache.org/jira/browse/JSPWIKI-465?focusedCommentId=12660676#
 action_12660676.

I would not go that route, actually I agree with Harry Metske in [1] in
that respect.

BTW: That CORBA and IOP package names are included with JDK is more a
sign of the quality of that code, than a good example (just my $.02).

BTW2: This is just a personal thought ..

Regards
Felix

[1]
https://issues.apache.org/jira/browse/JSPWIKI-465?focusedCommentId=12660689#action_12660689

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository

[Felix Meschberger]

Hi,

+1 (non-binding)

Regards
Felix

Jukka Zitting schrieb:
 Hi,
 
 We've had a number of long discussions about the incubating projects
 using the central Maven repository to distribute their releases. The
 current policy is that incubating releases should not go to there. The
 related discussion threads have died with no consensus but the issue
 still exists and affects many podlings. I would like to finally
 resolve the issue one way or another by calling the Incubator PMC to
 vote on the matter.
 
 In INCUBATOR-82 I have prepared a patch (also attached below) that
 changes the policy document to explicitly _allow_ extra distribution
 channels like the central Maven repository for incubating releases.
 Note that the proposed patch allows any such channels instead of
 focusing just on the Maven repository. Also, any releases must still
 be approved, comply with the disclaimer and naming rules, and be
 primarily distributed through the official
 http://www.apache.org/dist/incubator/ channel.
 
 Please vote on accepting or rejecting this policy change! This
 majority vote is open for a week and only votes from the Incubator PMC
 members are binding.
 
 [ ] +1 Yes, allow extra release distribution channels like the central
 Maven repository
 [ ] -1 No, keep the current policy
 
 My vote is +1
 
 BR,
 
 Jukka Zitting
 
 Patch from https://issues.apache.org/jira/browse/INCUBATOR-82:
 
 Index: site-author/incubation/Incubation_Policy.xml
 ===
 --- site-author/incubation/Incubation_Policy.xml  (revision 692094)
 +++ site-author/incubation/Incubation_Policy.xml  (working copy)
 @@ -489,6 +489,8 @@
  p
  Releases for empodling/em strongMUST/strong be distributed through
  codehttp://www.apache.org/dist/incubator/empodling/em/code.
 +In addition, the Podling MAY choose to distribute approved releases through
 +other channels like the central Maven repository.
  /p
/section
section id=Use+of+Apache+Resources
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [IP CLEARANCE] Apache Felix Simple Remote Shell

[Felix Meschberger]

Hi all,

Assuming lazy consensus as per the rules and assumes this to be cleared. 
Thanks.


I will now add this code basis to the Apache Felix project.

Regards
Felix

Felix Meschberger schrieb:

Hi,

The Apache Felix project has received a contribution of the Simple
Remote Shell from Dieter Wimberger

* The code is attached to the FELIX-615 JIRA issue [1]

* The IP Clearance form has been committed to the Incubator website. [2]

* A vote has passed on the [EMAIL PROTECTED] mailing list [3]

The clearance passes by lazy consensus if no -1 votes are cast within
the next 72 hours.

Thanks and Regards
Felix

[1] https://issues.apache.org/jira/browse/FELIX-615
[2] http://incubator.apache.org/ip-clearance/felix-remote-shell.html
[3] http://markmail.org/message/65ualfc4s2lnfkwz



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[IP CLEARANCE] Apache Felix Simple Remote Shell

[Felix Meschberger]

Hi,

The Apache Felix project has received a contribution of the Simple
Remote Shell from Dieter Wimberger

* The code is attached to the FELIX-615 JIRA issue [1]

* The IP Clearance form has been committed to the Incubator website. [2]

* A vote has passed on the [EMAIL PROTECTED] mailing list [3]

The clearance passes by lazy consensus if no -1 votes are cast within
the next 72 hours.

Thanks and Regards
Felix

[1] https://issues.apache.org/jira/browse/FELIX-615
[2] http://incubator.apache.org/ip-clearance/felix-remote-shell.html
[3] http://markmail.org/message/65ualfc4s2lnfkwz

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: report wiki page

[Felix Meschberger]

Hi

Brett Porter schrieb:

I've populated the report wiki page:
http://wiki.apache.org/incubator/August2008


Thanks, just added the Sling report.

Regards
Felix

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[RESULT] [IP CLEARANCE] Moving OSGi Console from Sling to Felix

[Felix Meschberger]

Hi all,

This clearance has passed. So I continue with moving the OSGi console
from Sling to Felix.

Thanks and Regards
Felix

Am Dienstag, den 13.05.2008, 12:48 +0200 schrieb Felix Meschberger:
 Please check clearance on:
 https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/felix-osgi-console.xml
 
 Thanks
 Felix


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[IP CLEARANCE] Moving OSGi Console from Sling to Felix

[Felix Meschberger]

Please check clearance on:
https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/felix-osgi-console.xml

Thanks
Felix


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [IP CLEARANCE] Moving OSGi Console from Sling to Felix

[Felix Meschberger]

Hi,

Am Dienstag, den 13.05.2008, 21:41 +0100 schrieb Robert Burrell Donkin:
 On Tue, May 13, 2008 at 11:48 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
  Please check clearance on:
   
  https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/felix-osgi-console.xml
 
 looks fine to me

Thanks.


 
 just FYI software grants are only necessary when importing code from
 outside the foundation

Right. I listed the grant because the origins of the code stems from
outside the foundation and where brought into the incubator as part of
the Sling project backed by the software grant.

Regards
Felix


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] RAT to enter incubator

[Felix Meschberger]

+1 (non binding)

Regards
Felix

Am Dienstag, den 30.10.2007, 22:03 + schrieb Robert Burrell Donkin:
 i'd like to propose that the IPMC sponsors the entry of RAT into the incubator
 
 - robert
 
 --8-
 [ ] +1 Allow RAT to enter incubator, sponsored by IPMC
 [ ] +0
 [ ] -0
 [ ] -1 Do no allow RAT to enter incubator
 ---
 
 Rat Proposal
 ...


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: (confluence) wiki site ?

[Felix Meschberger]

Hi Jim,

Look here http://cwiki.apache.org/CWIKI towards the middle of the page
is a fine description on how to use the autoexported Confluence space as
your project's site.

Hope this helps as a first shot.

Regards
Felix


Am Mittwoch, den 19.09.2007, 11:21 -0400 schrieb Jim Hurley:
 The River project is considering changing its project area
 from a velocity site which was originally setup to a confluence
 wiki site (or maybe now that JSPWiki is going to be an incubating
 project, that would be a better wiki choice?).
 
 Looking for advice/pointers/help on specifically how we could
 accomplish that.
 
 thanks -Jim
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: FastFeather and ApacheCon - incubator's place to shine!

[Felix Meschberger]

Hi all,

I will attend ApacheCon and would be happy to get a slot to present the
Apache Sling project.

Thanks and Regards
Felix

Am Montag, den 10.09.2007, 15:07 -0500 schrieb William A. Rowe, Jr.:
 Hello incubator committers!
 
 You should have received an email from me if you are a committer,
 sent on 8/17, encouraging you to attend ApacheCon US 2007.  You might
 or might not know that early registration discounts are extended still
 until September 22nd, so you have a week and a half still to save some
 wampum on your registration!
 
 But this is going to you now because tomorrow night we are finalizing
 the next press release about ApacheCon, and we want to generate excitement.
 What's more exciting than tomorrows' next big thing?  That would be here
 at the Apache Incubator and at Apache Labs!  See the press release below
 for how this was sold in the past.
 
 If you 1) plan to attend and 2) are willing to present a 15 minute short
 presentation about your incubating or labs technology, the attendees would
 very much appreciate learning about your podling's technology!  These have
 been warmly received, the attendees are very kind to folks who haven't done
 that much public speaking.  And you get the satisfaction of championing
 your podling!
 
 Lars is starting the schedule soon, and is willing to modify it (space
 available) all the way through the convention.  But for the purpose of
 identifying what technologies are represented, **please reply** with the
 project *you* are willing to speak about to the general@ list, so everyone
 finds out about all the projects that will Fast Feather.  Do so today
 (in the next 24 hours) and *your project* can appear in the next official
 press release about the convention!
 
 Many thanks, see you in Atlanta!
 
 Bill
 
 
 
 
 from the AC/EU 2007 press release...
 
 FAST FEATHER TRACK – ALL DAY Thursday
 Due to the overwhelming response to the Incubator Fast Track in Austin at
 ApacheCon US 2006, we expanded the idea for Amsterdam – AND IT WAS A HIT.
 
 The ASF is now over 10 years old, with more than forty top level projects and
 dozens of other active projects in the Incubator and elsewhere. Additionally,
 there are new ideas and potential projects being hatched in the Incubator and
 Labs every day.
 
 With this in mind, we bring you the Fast Feather Talks. An extra session track
 has been added for Thursday. Join us in an intimate setting to hear 10 to 15
 minute updates on some of your favorite (or soon-to-be favorite!) projects
 within the ASF community. Stay for a few talks, or stay all day and get caught
 up on the exciting, cutting-edge world of ASF projects!
 
 Incubator: incubator.apache.org/
 
 The Incubator is the entry path into The Apache Software Foundation (ASF) for
 projects and codebases wishing to become part of the Foundation's efforts. All
 code donations from external organizations and existing external projects
 wishing to join Apache enter through the Incubator.
 
 Labs: labs.apache.org/
 
 Apache Labs is a place for innovation where committers of the foundation can
 experiment with new ideas. The aim is to provide the necessary resource to
 promote and maintain the innovative power within the Apache community without
 the burden of community building.
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PROPOSAL] JSPWiki

[Felix Meschberger]

Hi Janne,
 
Am Donnerstag, den 30.08.2007, 00:02 +0300 schrieb Janne Jalkanen:
 Abstract
 
 Apache JSPWiki will be a modular and user-extensible wiki-engine,  
 based on the open source JSPWiki software.
 ...
  * Clean up our metadata and backend support by adding JSR-170  
 repository support
  * Adoption of a more flexible web framework (Stripes, an Apache- 
 licensed project)

This is interesting. Have you seen, that we are currently voting on the
Jackrabbit list to enter Sling into the incubator. You may find more
information at [1].

I could imagine, that this would probably be very helpful for your
project.

Regards
Felix

[1] http://wiki.apache.org/jackrabbit/ApacheSling


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Proposal] Sling

[Felix Meschberger]

Hi

Am Samstag, den 18.08.2007, 21:25 +0200 schrieb Gianugo Rabellino:
  Anyone interested in mentoring Sling?
 
 Count me in.

Thanks, your listed.

Regards
Felix



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Proposal] Sling

[Felix Meschberger]

Hi Noel,

 Seems to me that you might want to consider a binding for JSR-286 Portlets
 (using the Event mechanism to deliver the content to be rendered), rather
 than create a totally new UI component framework.  I can't see any reason
 why the nested includes would be an issue.
 
 Just a thought, and one that would need to be fleshed out.

As Alex also pointed out, the goal is to have a flexible framework to
allow for different bindings. I would just add that JSR-311 might also
be an option.

Perhaps, those bindings will be required sooner or later but should be
easy to do.

Regards
Felix


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Proposal] Sling

[Felix Meschberger]

Am Donnerstag, den 09.08.2007, 09:27 -0700 schrieb Eelco Hillenius:
  I would like to propose a new Apache project named Sling. The proposal
  text is attached to this message and can also be found at [1].
 
 +1.

Thanks :-)

 It seems to be primarily focussed on content delivery, not so much
 interactivity, right?

Yes and no. Currently, only content delivery is supported. But it is
foreseen, that we have a need for interactive applications, such as for
example support for JSR-311, but also Portlet, JSF, etc...

  As such it would handle a sub set of what most
 other web frameworks out there now try to achieve, which makes me
 wonder whether you are planning on interoperability with other
 frameworks as a core feature?

Definitely. While we have no concept yet, I assume something like
pseudo-content which could be registered as a service (in OSGi terms)
and which could be used to resolve the Content instance from the URL.
This would easily fit in the model.

Regards
Felix


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Proposal] Sling

[Felix Meschberger]

Hi Noel,

Am Mittwoch, den 08.08.2007, 23:12 -0400 schrieb Noel J. Bergman:
  As such each request URL addresses a Content object which in turn
  resolves to a Component, which finally is responsible for handling
  the request and providing a response.
 
 And this differs from a Servlet/Portlet, how?

With Servlet/Portlet the URL resolves to the Servlet/Portlet directly
and the Servlet/Portlet has to care for itself to acquire the data to
act upon. With Sling, the framework resolves the URL to data and from
the data resolves the Component (the entity corresponding to
Servlet/Portlet). When the Component is called, the data is provided to
the Component and the Component does not have to care about getting to
it.

  Recognizing the need to componentize development of Web
  Applications and have easy mix and match for such
  components to build web pages, the basic building blocks
  of web pages are called components.
 
 Differing from JSR-168/JSR-286 Portlets, how?  Other than by leveraging the 
 OSGi core service platform specification?

In some sense components are comparable to Portlets. But while a Portlet
just cares to render itself and generally does not know anything about
the other portlets (obviously JSR-286 tries to overcome this limit). In
Sling on the other hand, there is now almighty mother container, which
knows about all components on a page to render.

Sling just resolves the URL to data and to a Component. This component
then is responsible for rendering the complete page or finding more data
to be included. Include means, the data (in terms of a Java object
implementing the Content interface) is given to Sling to resolve the
Component to call. At the end of the page rendering process, Sling has
just actively resolved the initial data/Component and was involved in
further processing but did not control the actuall process.

Consider a page containing a page title and a paragraph system, which in
turn consists of a series of paragraphs. With Sling, the Component
responsible for the page would call include the page title and the
paragraph system content. The paragraph system content in turn would
include all paragraphs inside the paragraph system without the page
component knowing about this at all.

 
 Obviously, looking for some details.  But not such that I'm voting on the 
 answer.

I hope, this helps shed some more light on it.

Regards
Felix


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Proposal] Sling

[Felix Meschberger]

 store 
  * Uses Jackrabbit OCM to map Repository Items to Java Objects 
  * Internally deals with Java Objects 
  * Built as OSGi Bundles supporting any compliant OSGi framework 
  * Provides integration into Apache Felix for launching and OSGi
services support 
  * Componentized data model allowing flexible web application
building 
  * Based on standard Servlet API 
  * Open to allow support for web application complying with REST
architectural style 
  * Each Node for which a valid Jackrabbit OCM mapping exists may be
addressed by URL 

Initial Goals
Establish Sling as the content centric web application framework for JCR
repositories. As such, it is intended for Sling to mature into a
subproject of Apache Jackrabbit. 


Current Status
Meritocracy
We plan to do everything possible to encourage an environment that
supports a meritocracy. 


Community
By proposing this project to the Incubator for inclusion as subproject
of Apache Jackrabbit we hope grow Sling into first class web application
framework which leverages the know-how of the Apache community. 


Core Developers
The project was founded be Felix Meschberger in late 2006 at Day.
Currently only Day employees work on this project, though this will
change as soon as we get a chance to invite more people to join this
effort. In fact the initial committer list already contains several
people not related to Day. 


Alignment
Sling is targeted to be deployed into any compliant OSGi framework. To
support HTTP requests Sling interoperates with the OSGi HttpService.
This allows deployment of the framework inside a Servlet API compliant
servlet container given appropriate bridging or the framework may be run
as a standalone application, where an implementation of the OSGi
HttpService handling the HTTP requests is deployed. 

To access content addressed by URLs, Sling depends on any compliant
implementation of the JCR API, such as Jackrabbit, plus the Jackrabbit
Object Content Mapping. 


Known Risks
Orphaned products
This is an active project within Day Software and will be the basis of
ongoing work of Day's own content management products, such as Digital
Asset Manager. In addition, it is foreseen, that Web services of
Jackrabbit may be ported to Sling. 


Inexperience with Open Source
All committers have experience working on open source projects and
several are veterans at Apache. 


Homogenous Developers
Sling is currently being developed only by Day employees, but we hope
that the framework will attract interest from other individuals and
companies. 


Reliance on Salaried Developers
Most of the developers are paid by their employer to contribute to this
project, but given the anticipation from the Java community for Sling
the committers' sense of ownership for the code, the project would
continue without issue if no salaried developers contributed to the
project. 


Relationships with Other Apache Products
  * Apache Jackrabbit 
  * Apache Felix 

A Excessive Fascination with the Apache Brand
Day actively contributes to Apache Jackrabbit and other Apache projects,
and the individuals behind the Sling project feel that an Apache
community would be the best environment for the codebase to grow and
attract new users and contributors. 


Documentation
Initial Documentation is made available on the Jackrabbit Wiki pages at
ApacheSling. 


Initial Source
Currently Sling is a closed source project. For this reason the source
can only be opened upon the acceptance of the project as an Apache
Incubator project by the IPMC. Upon the acceptance of the project and
submission of the Software Grant by Day, the source code will be
committed to the Apache SVN repository. 


Source and Intellectual Property Submission Plan
The code base will be licensed to the ASF using a software grant from
Day, allowing Apache to relicense as pure Apache License 2.0 code.


External Dependencies
Besides depending on two Apache projects, namely Jackrabbit and Felix,
Sling depends on the OSGi API libraries, which are made available as
part of the Apache Felix project under the Apache License 2.0. 


Cryptography
  * none 

Required Resources

Mailing lists
  * sling-dev at incubator.apache dot org 
  * sling-commits at incubator dot apache dot org 
  * sling-private at incubator dot apache dot org 

Subversion Directory
  * https://svn.apache.org/repos/asf/incubator/sling 

Issue Tracking
  * JIRA Sling (SLING) 

Java Packaging
  * All Sling classes live inside and below sling. It is foreseen to
root sling at org.apache such as to have all Sling classes at or
below org.apache.sling. 

Other Resources
  * none 

Initial Committers
  * Felix Meschberger (fmeschbe at apache dot org) 
  * Carsten Ziegeler (cziegeler at apache dot org) 
  * Bertrand Delacretaz (bdelacretaz at apache dot org

Re: [Proposal] Sling

[Felix Meschberger]

Hi Alex,

Am Mittwoch, den 08.08.2007, 17:03 +0300 schrieb Alexandru Popescu ☀:
 Very interesting initiative Felix! Still, I am wondering why this
 would not start as a Jackrabbit contrib project, and I don't think I
 have seen this in the attached proposal.

The reason for not simply adding it as a contrib to Jackrabbit is the
size of the project: It consists of roughly 30 sub-projects. Pushing a
project of this size simply as a contrib to an existing project has been
considered as going through the backdoor and not being the Apache way.

I have not taken a note on this in the proposal because we just could
not imagine just hacking it into Jackrabbit as a contrib.

Hope this helps.

Regards
Felix


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]