from:"Scott Wilson"

Re: Looking for a Champion for ORDs

2015-09-16 Thread Scott Wilson


> On 16 Sep 2015, at 10:49, Atri Sharma  wrote:
> 
> Just to clarify, I intend to help out project since this is a PostgreSQL
> based project and I have experience in PostgreSQL. Since I am not an IPMC
> member, I cannot be a mentor, hence just offered to help. I do not intend
> to code in the project due to time limitations, but would love to help out
> in the necessary areas if I can.

PostgreSQL clustering, configuration and virtualisation is an important part of 
the project, and your advice here will be very helpful - thanks for 
volunteering Atri!

> 
> On Wed, Sep 16, 2015 at 1:33 PM, Kris Popat  wrote:
> 
>> Thanks Chris, I’ve put the proposal up on the wiki now.
>> As you suggested it’s at http://wiki.apache.org/incubator/ORDSProposal <
>> http://wiki.apache.org/incubator/ORDSProposal>
>> 
>> Any comments and suggestions are welcome.
>> 
>> Cheers
>> 
>> Kris
>> 
>>> On 15 Sep 2015, at 16:46, Mattmann, Chris A (3980) <
>> chris.a.mattm...@jpl.nasa.gov> wrote:
>>> 
>>> Dear Kris, please feel free to post the full proposal to the
>>> Incubator wiki, here:
>>> http://wiki.apache.org/incubator/, e.g., at:
>>> http://wiki.apache.org/incubator/ORDSProposal
>>> 
>>> 
>>> You will need permissions to do so, so let someone on this list
>>> know when you register for your wiki account.
>>> 
>>> Sounds very interesting.
>>> 
>>> Cheers,
>>> Chris
>>> 
>>> ++
>>> Chris Mattmann, Ph.D.
>>> Chief Architect
>>> Instrument Software and Science Data Systems Section (398)
>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> Office: 168-519, Mailstop: 168-527
>>> Email: chris.a.mattm...@nasa.gov
>>> WWW:  http://sunset.usc.edu/~mattmann/
>>> ++
>>> Adjunct Associate Professor, Computer Science Department
>>> University of Southern California, Los Angeles, CA 90089 USA
>>> ++
>>> 
>>> 
>>> 
>>> 
>>> 
>>> -Original Message-
>>> From: Kris Popat 
>>> Reply-To: "general@incubator.apache.org" 
>>> Date: Tuesday, September 15, 2015 at 6:08 AM
>>> To: "general@incubator.apache.org" 
>>> Subject: Looking for a Champion for ORDs
>>> 
 Hello All,
 
 A while back I started a brief discussion about inclubating ORDS (Oxford
 Research Database System). However, we had a pause in this process over
 the summer whilst some potential IP issues were sorted out, these have
 been resolved.
 
 I would like to start looking for a Champion for the project again.
 
 Here is the first section of the proposal which has some adjustments
>> from
 the previous post.
 
 --
 ORDS is a user and project centered, web-based  database-as-a-service
 (DbaaS) system with data publishing.
 
 ORDS imports data from recognized sources such as csv files,
 spreadsheets, and relational database files into structured online
 databases to provide DbaaS functionality. The databases are stored in an
 RDBMS (PostgreSQL with ORM access). It has a full set of high-level
>> tools
 for managing and editing these databases, including tools that give
>> users
 the ability to create versioned snapshots of data and share specific
 datasets. New databases can also be created using these tools.
>> Databases
 are housed in projects and associated with users with given roles. The
 data can be exported in common formats.
 -
 
 We believe strongly that the ASF would be good place for this project to
 grow because of it’s tradition of upholding good open source practice.
 
 In brief it is in use by researchers at Oxford and there is a lot of
 interest in the sector for using it in other institutions.  Promotion of
 the system is already happening and this should give us a route for
 getting users, documenters, testers and developers involved.
 It is written in Java and uses Tomcat, PostgreSQL though the database
>> can
 be switched as we use JPA for all db access.
 
 I have worked on the full proposal and can post it on this list if
 required or will put it on the wiki as and when is appropriate.  I just
 didn’t want to clog this email with a whole proposal at this stage.
 
 Please let me know if you are interested in Championing this project or
 know of any member who might be.
 
 Many thanks
 
 Kris Popat
 
 ———
 Developer | Consultant Researcher
 
 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
>>> 
>>> 
>>>

Re: graduated incubator podling status pages cleanup?

2012-12-27 Thread Scott Wilson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 27 Dec 2012, at 02:02, David Crossley wrote:

 Mark Struberg wrote:
 hi lords and ladies!
 
 I looked at a few of my old incubation projects I helped to grow and most of 
 them still don't have their incubator status page [1] marked as 'graduated'.
 
 Is there a good example at where I can look at how to mark those projects as 
 such?
 
 Is simply writing a 'YES' under the last few questions is enough? The 
 summary page [2] does look fine at least.
 
 Perhaps Wookie is a recent example.
 
 However not many seem to update that section.

Oops, missed the last questions at the end. I've just filled those in for 
Wookie now. 

I'm not sure if you can set the status of the project metadata page to 
graduated - as far as I can tell you just modify podlings.xml to update the 
summary page. On the project page the only thing you can do is answer those 
questions, and add an item to the news list saying when the project has 
graduated.

 
 When we do find a decent example, then link it to the docs.
 
 The help for Clutch tries to assist:
 http://incubator.apache.org/clutch.html#h-Graduate
 
 Many graduated projects still need to attend to their
 project metadata and tidy up after themselves.
 
 -David
 
 LieGrue,
 strub
 
 
 [1] http://incubator.apache.org/projects/isis.html
 [1] http://incubator.apache.org/projects/
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJQ3KIdAAoJEB9Shkh1DfjWUyQP/jrTMTNLWw28CucCVqJGMDx3
UwZl8bHADSZEbyYMa66NY+rWNxQvQ8XMqDbQKhnfrGtPmpjOP9fI0tIKK0E519ny
PWXwIio9N8ENV6fOyGSRJqDtl+ky//ia4Vl4dK4yHrjdjFeHVao6Eu+cyfghpM4f
cWlUyV70ym03bpQOpEuIoMq+0V4F8gpVnqWl2dX6RP4ogOlg0zCZo+R046r51Yqr
NVReZ86IcT4EhGbJZyqy/mfIgGS7ORzgf5OwnxYRQjUYjYvwaV723LS5G4TVM7uC
Z/B9bw4QHzdZwtyd3Z3RLVm0KZ0p/qLJRlb7gshzsNSUmR5fhYFkHQRl2iHagaUr
T4MQkj6WmupSwUEOWoM/TvZvUMzFRdLMrasqFvDMtdKkOOSkUmpnXoV+68x/WlnM
smd6voj/tAdqi5XTkrHLh9xpe8TkEgIfPAPzTiJjXi+3t53e4FusqwzsNWqrSJoF
IXdi20yircBAPsA+zeKAsZiXGgTJvX+buHnwwdE1fCJZSOjOF6QGlv5Kq4wuvEfO
BVALb8IyexPwCQmrACu1+9yqztreQn2ettK3PcusjtdTkV5NuYzY4dxdsoLuTIBF
pG2YpClbbAO89jWp6jxINyWHtMCy0EaDS33+pJ3I9KkqJxqlfHp1i41omdMk8zp4
MK/5DA26uyZ8W8jWncWb
=lLfT
-END PGP SIGNATURE-

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

Re: [VOTE] Accept Apache Streams as an Incubator Project

2012-11-14 Thread Scott Wilson

+1

On 14 Nov 2012, at 15:24, Ross Gardler wrote:

 +1
 
 (Love the idea of Apache Screams, we could then have a Wookie Scream in a
 Rave)
 

+100

 Ross
 
 -Original Message-
 From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
 Sent: 14 November 2012 14:49
 To: general
 Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project
 
 Hi,
 
 On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B.
 mfrank...@mitre.org wrote:
 Please vote.
 
  [x] +1 Accept Streams into the incubator
 
 Though I do think there's some life also in the alternative name, Apache
 Screams, that came up in discussion during ACEU. ;-)
 
 BR,
 
 Jukka Zitting
 
 -
 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: Adobe (formally Macromedia) Authorware - Developed by Michael Allen

2012-11-05 Thread Scott Wilson

Hi Andrew,

You also might want to consider joining the Xerte[1]  community - its not the 
same software but does roughly the same thing, and perhaps you could help it 
provide some of the features you liked best in Authorware.

S

[1]  http://www.nottingham.ac.uk/xerte/

On 2 Nov 2012, at 15:23, strate...@metrocast.net strate...@metrocast.net 
wrote:

 Hello,
 
 Authorware is an excellent icon based eLearning development environment.  
 Adobe states that they are discontinuing this product.  As an educator with 
 an interest in software development, I’d hate to see this outstanding 
 software become a historical footnote.  
 
 If Adobe could be persuaded to donate Authorware to the OpenSource community 
 could it have a home with Apache?  How would this process take place?  How 
 would I get the ball rolling?
 
 Thanks.
 
 - Andrew


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

[RESULT] [VOTE] Graduate Wookie podling from the incubator

2012-10-31 Thread Scott Wilson

The Vote started on 2012-10-24 has ended.

Results:

+1 Ross Gardler (IPMC)
+1 Luciano Resende (IPMC)
+1 Bertrand Delacretaz (IPMC)
+1 Jean-Baptiste Onofré (IPMC)
+1 Andrew Savory (IPMC)
+1 Matthew Franklin (IPMC)
+1 Jukka Zitting (IPMC)
+1 Suresh Marru (IPMC)
+1 Ate Douma (IPMC)
+1 Raminderjeet Singh
+1 Sander van der Waal

There were no other votes cast.

Tally (IMPC): 9  +1 votes, no 0 votes, no -1 votes.

The IPMC has approved the proposal to recommend the resolution to the Board. 
I'll now proceed and send an email to the Board asking to include the 
resolution (as amended below - thanks Suresh and Jukka) in the agenda for the 
next Board meeting.

Thanks everyone,

S

===
X. Establish the Apache Wookie 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,  for distribution at no charge to 
 the public, related to an implementation of the W3C Widgets
 family of specifications.

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

 RESOLVED, that the Apache Wookie Project be and hereby is
 responsible for the creation and maintenance of software
 related to implementation of the W3C Widgets family of 
 specifications; and be it further

 RESOLVED, that the office of Vice President, Apache Wookie 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 Wookie Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache Wookie 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 Wookie Project:

 * Scott Wilsonscot...@apache.org 
 * Ate Douma   a...@apache.org
 * Ross Gardlerrgard...@apache.org
 * Matt Franklin   mfrank...@apache.org
 * Paul Sharples   psharp...@apache.org
 * Kris Popat  krispo...@apache.org
 * Raido Kuli  ra...@apache.org
 * Hoang Minh Tien h...@apache.org


 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Scott Wilson
 be appointed to the office of Vice President, Apache Wookie, 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 Wookie 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 Wookie Project; and be it further

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

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Wookie 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

[VOTE] Graduate Wookie podling from the incubator

2012-10-24 Thread Scott Wilson

This is a call for vote to graduate the Wookie podling from Apache Incubator.

Wookie entered the Incubator in July of 2009. During incubation, Wookie has:

* Produced 5 releases
* Added 3 new Committer/PPMC members
* Cleared IP on all donations
* Learned to self-govern and engage the community
* Received and applied multiple community patches

The Wookie community has voted to proceed with graduation [1] and the result
can be found at [2].

Please VOTE on the resolution below:

[ ] +1 Graduate Wookie from the Incubator per the resolution below.
[ ] +0 Don't care.
[ ] -1  Don't graduate Wookie from the Incubator because..

This vote will be open for at least 72 hours.

[1] http://markmail.org/message/jcgdcacn535jqwqy
[2] http://markmail.org/message/hp2bggjhec7vpdch

==

X. Establish the Apache Wookie 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 an implementation of the
   W3C Widgets family of 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 Wookie Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Wookie Project be and hereby is
   responsible for the creation and maintenance of software
   related to implementation of the W3C Widgets family of 
   specifications; and be it further

   RESOLVED, that the office of Vice President, Apache Wookie 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 Wookie Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Wookie 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 Wookie Project:

* Scott Wilsonscot...@apache.org  
   * Ate Douma   a...@apache.org
   * Ross Gardlerrgard...@apache.org
   * Matt Franklin   mfrank...@apache.org
   * Paul Sharples   psharp...@apache.org
   * Kris Popat  krispo...@apache.org
   * Raido Kuli  ra...@apache.org
   * Hoang Minh Tien h...@apache.org


   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Scott Wilson
   be appointed to the office of Vice President, Apache Wookie, 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 Wookie 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 Wookie Project; and be it further

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

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

[jira] [Resolved] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-19 Thread Scott Wilson (JIRA)


 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Wilson resolved PODLINGNAMESEARCH-13.
---

Resolution: Fixed

 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-19 Thread Scott Wilson (JIRA)


[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13480021#comment-13480021
 ] 

Scott Wilson commented on PODLINGNAMESEARCH-13:
---

After examination of the results of this search and discussion with trademarks, 
the Wookie PPMC has decided to continue with the name Apache Wookie.

 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Re: [VOTE] Ripple Emulator to be admitted to the incubator

2012-10-11 Thread Scott Wilson

+1 (non-binding)

On 11 Oct 2012, at 18:04, Gord Tanner wrote:

 Please cast your votes!
 
 [ ] +1, recommend Ripple to move into the incubator
 [ ] +0, abstain/don't care
 [ ] -1, do not recommend Ripple to move into the incubator,because...
 
 
 
 Ripple, A Mobile Environment Emulator
 =
 
 Abstract
 
 
 Ripple is a browser based mobile phone emulator designed to aid in the
 development
 of HTML5 based mobile applications.  Ripple is a cross platform and cross
 runtime testing/debugging tool. It currently supports such runtimes as
 Cordova, WebWorks
 and the Mobile Web.
 
 Proposal
 
 
 Ripple is going to be (in some circles already is) the goto emulator
 for rapid development of mobile web applications. This
 will be accomplished by quickly keeping up with the mobile web
 platforms as they arise (Cordova, Tizen, WAC, WebWorks, etc).
 
 Background
 ==
 
 Ripple started as a product of tinyHippos and was aquired by Research
 in Motion in late March 2011.  Ripple was then open sourced
 under the Apache 2.0 License and hosted on the blackberry github
 account (http://github.com/blackberry/Ripple-UI).
 
 Ripple is a browser based mobile phone emulator that runs as a chrome
 extension.  It fills the gap for developers between
 developing on their desktops/laptops and having to test on platform
 specific emulators or physical devices. Ripple allows develors
 to quickly edit-refresh-test in Chrome on their desktops/laptops while
 working on web content that will be embedded and distributed
 as a native application.
 
 Rationale
 =
 
 The project is currently opensourced and managed by a small team at
 Research in Motion.  We are starting to have some
 more community engagement but the project could benefit from greater
 exposure in the open source cummunity.  Our team
 overlaps highly with the Cordova group. Watching the success for that
 project in Apache has inspired us to contribute
 Ripple to the ASF as well.
 
 Ripple fills a large gap in the toolset for most mobile web developers
 between development on the desktop and testing
 on the physical device.
 
 Current Status
 ==
 
 Currently all development is managed on github via the issues and the
 direction of the project is strongly influenced by
 Research in Motion.  A more clear project plan and more open
 communication will be needed by this project to abide by
 the apache guidelines.
 
 Metriocracy
 ===
 
 Ripple has been very accepting of letting in patches from 3rd party
 developers and has been functioning like apache in requiring a CLA
 for code to be pulled in. The core team is hoping to grow and include more
 developers.
 
 Community
 =
 
 The development community of Ripple is a small but tight knit group but
 the users of the project number more than 40,000. With the launch
 ofemulate.phonegap.com (which is a portal for installing ripple) we
 are
 getting approx 5000 hits a day to that site.
 
 
 Core Developers
 ===
 
 See Inital Committers below.
 
 Alignment
 =
 
 Apache is a good match for this project due to it's close ties
 to the Cordova Project. Cordova has been very successful as a project
 since joining Apache and we hope Ripple will follow suit.
 
 Known Risks
 ===
 
 Orphaned Products
 -
 
 Ripple is a core component to the toolset at RIM and the Cordova /
 Phonegap community has embrased ripple into their tooling
 as well. This project has been under active development for 3 years
 and a lot of vested interest from both RIM and the
 community is already present to keep the tool up to date.
 
 Inexperience with Open Source
 -
 
 Ripple has been opensourced at RIM for the last year.  All of the work
 is done in the open. There are a few extra measures we need to learn
 how to take (mailing lists, project planning) for working within the
 ASF community.
 However the team has a good understanding of what needs to happen, as
 some of the
 team are also contributers to the Apache Cordova Incubator project.
 
 Homogenous Developers
 --
 
 Ripple's core team currently all works at RIM with contributions for
 some features done by third parties.  There is a
 backlog of features currently done / being put in by third parties
 such as Adobe and IBM.
 
 Reliance on Salaried Developers
 ---
 
 Most of the developers are paid by their employer to contribute to
 this project but are all highly involved on a personal
 level with this project as well as the mobile web community.
 
 Relationships with Other Apache Products
 
 
 There is a strong overlap and relationship between the ripple and
 cordova teams.  Gord Tanner is an active commiter in
 both project and has been ensuring that both projects progress together.
 
 An Excessive Fascination with the Apache Brand.

[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)


 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Wilson updated PODLINGNAMESEARCH-13:
--

 Evidence Of Open Source Adoption: 
A search on Github for Wookie yields 14 repositories: 

- 7 of these are plugins for Apache Wookie, or ports of the Apache Wookie W3C 
library jar to other platforms/languages 
- alto/wookie is a Rails plugin for exporting stats; last updated 3 years ago 
- CaioMatias/Wookie is a Flash project framework 
- BookieWookie is a link-sharing plugin for Rails; last updated 3 years ago 
- wookie-translator is an english-to-wookie translator (probably a 
misspelling of Wookiee from Star Wars) 
- wookie-cab- is an empty project 
- wookie-cam is an empty project 
- fernandoafb/wookie is an empty project

A search on Sourceforge for Wookie yields 1 project: 

http://wookilang.sourceforge.net/; 

This is the Wooki Language Interpreter project (wookilang) 

This project was registered on SourceForge.net on Apr 17, 2011, and is 
described by the project team as follows: 

It is a language and interpreter aiming to test data structures, with debugging 
tools.
Evidence Of Use On World Wide Web: 
A Google search for Wookie Software shows Apache Wookie as the top 3 results; 
the 4th result is a reference in a course description to Wookie as a 
software simulator for Windows that can simulate the function of a real 68HC11 
microcontroller (http://www.ele.uri.edu/courses/ele205/Lab03.pdf). Further 
searches show references in a few other electronics course descriptions, as 
recently as 2009. 

Much further into the results is a reference to WookieChat - and IRC client for 
the AmigaOS: 
http://wookiechat.amigarevolution.com/wookiechat/ 

There are also some references to a radio-related application on some forums, 
e.g.: 

2100-WOOKIE-LAB- Field Programmer for the MOBIUS Radio-Series (Sky Walker) 
2100 portables and mobiles radio with 5/6 Tone signalizing. v.R2.01beta 
SDVN4274A. 

Is dus Wookie lab software, is een Beta en daarom is hij niet volledig 100% 
betrouwbaar. Dat uit zich in het soms niet kunnen benaderen van de tuningmodus. 
Wookie wil bij het opslaan van je codeplug nog wel eens alle kanalen op 
eenzelfde frequentie zetten. Soms kun je met een nieuwe installatie wel in de 
tuningmodus komen. Maar de beste oplossing om dit uit te laten voeren door 
iemand met kennis van zaken (en die gebruikt de Ms-Dos RSS versie!). 

http://www.scannerforum.nl/index.php?topic=6418.0 

Updated results of searches for open source and WWW use.

 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)


[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471273#comment-13471273
 ] 

Scott Wilson commented on PODLINGNAMESEARCH-13:
---


Searched for Wookie projects at http://www.ohloh.net/ yields 12 results

- Apache Wookie is the top result
- Wookie-Army [no code, and no description]
- spreadthesource's wooki [Wooki* is a smart tool to write documents. It let 
you publish them and get reviews.]
- JabberWookie Jabber Library for Java [Yet another Jabber library, written in 
Java (to the 1.1 spec). The goal of which is to be as simple to use and 
understand as possible. (Depends on the SSTTR Java Library).]
- Apache Rave [depends on Apache Wookie]
- groovy-option-parser [the term wookie turns up in its description as an 
example of a parameter name]
- wookiesareback [wookies threading project]
- Rave in Context [depends on Apache Wookie]
- Wooky [Wooky is a free tile map editor for the creation of tile based 
games.]
- Jiss [A simulator for the M68HC11 microcontroller written in Java, based on 
the Wookie HC11 Simulator sources.]
- maroon-harvest [Like Star Wars, But With Salukis Instead of Wookies]
- quote-unquote [A quote database (QDB) engine using the CakePHP framework and 
an SQL database. This code is very close to the version powering the Wookiee' 
QDB, and was originally custom-written for that site]



 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)


 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Wilson updated PODLINGNAMESEARCH-13:
--

Evidence Of Open Source Adoption: 
A search on Github for Wookie yields 14 repositories: 

- 7 of these are plugins for Apache Wookie, or ports of the Apache Wookie W3C 
library jar to other platforms/languages 
- alto/wookie is a Rails plugin for exporting stats; last updated 3 years ago 
- CaioMatias/Wookie is a Flash project framework 
- BookieWookie is a link-sharing plugin for Rails; last updated 3 years ago 
- wookie-translator is an english-to-wookie translator (probably a 
misspelling of Wookiee from Star Wars) 
- wookie-cab- is an empty project 
- wookie-cam is an empty project 
- fernandoafb/wookie is an empty project

A search on Sourceforge for Wookie yields 1 project: 

http://wookilang.sourceforge.net/; 

This is the Wooki Language Interpreter project (wookilang) 

This project was registered on SourceForge.net on Apr 17, 2011, and is 
described by the project team as follows: 

It is a language and interpreter aiming to test data structures, with debugging 
tools.


A search for Wookie projects at http://www.ohloh.net/ yields 12 results in 
the following order:

- Apache Wookie
- Wookie-Army [no code, and no description]
- spreadthesource's wooki [Wooki* is a smart tool to write documents. It let 
you publish them and get reviews.]
- JabberWookie Jabber Library for Java [Yet another Jabber library, written in 
Java (to the 1.1 spec). The goal of which is to be as simple to use and 
understand as possible. (Depends on the SSTTR Java Library).]
- Apache Rave [depends on Apache Wookie]
- groovy-option-parser [the term wookie turns up in its description as an 
example of a parameter name]
- wookiesareback [wookies threading project]
- Rave in Context [depends on Apache Wookie]
- Wooky [Wooky is a free tile map editor for the creation of tile based 
games.]
- Jiss [A simulator for the M68HC11 microcontroller written in Java, based on 
the Wookie HC11 Simulator sources.]
- maroon-harvest [Like Star Wars, But With Salukis Instead of Wookies]
- quote-unquote [A quote database (QDB) engine using the CakePHP framework and 
an SQL database. This code is very close to the version powering the Wookiee' 
QDB, and was originally custom-written for that site]


  was:
A search on Github for Wookie yields 14 repositories: 

- 7 of these are plugins for Apache Wookie, or ports of the Apache Wookie W3C 
library jar to other platforms/languages 
- alto/wookie is a Rails plugin for exporting stats; last updated 3 years ago 
- CaioMatias/Wookie is a Flash project framework 
- BookieWookie is a link-sharing plugin for Rails; last updated 3 years ago 
- wookie-translator is an english-to-wookie translator (probably a 
misspelling of Wookiee from Star Wars) 
- wookie-cab- is an empty project 
- wookie-cam is an empty project 
- fernandoafb/wookie is an empty project

A search on Sourceforge for Wookie yields 1 project: 

http://wookilang.sourceforge.net/; 

This is the Wooki Language Interpreter project (wookilang) 

This project was registered on SourceForge.net on Apr 17, 2011, and is 
described by the project team as follows: 

It is a language and interpreter aiming to test data structures, with debugging 
tools.


 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)


 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Wilson updated PODLINGNAMESEARCH-13:
--

Evidence Of Registration: 
I conducted a US Trademark Search, this shows no results for Wookie:

http://www.trademarkia.com/trademarks-search.aspx?tn=wookiefs=01/01/1960fe=08/02/2012pri=009gs=cn=st=1

I searched at Trademarkia. This showed 3 results for Wookie, 2 were ABANDONED 
and 1 was CANCELLED. None were software-related (action figures, flavoured 
nuts, canteen services).

  was:
I conducted a US Trademark Search, this shows no results for Wookie:

http://www.trademarkia.com/trademarks-search.aspx?tn=wookiefs=01/01/1960fe=08/02/2012pri=009gs=cn=st=1


 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)


 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Wilson updated PODLINGNAMESEARCH-13:
--

Evidence Of Registration: 
I conducted a US Trademark Search, this shows no results for Wookie:

http://www.trademarkia.com/trademarks-search.aspx?tn=wookiefs=01/01/1960fe=08/02/2012pri=009gs=cn=st=1

I searched at Trademarkia. This showed 3 results for Wookie, 2 were ABANDONED 
and 1 was CANCELLED. None were software-related (action figures, flavoured 
nuts, canteen services).

I searched on TESS and found 1 live trademark matching Wookie:

* Word Mark PROFESSIONALWOOKIE Goods and Services IC 035. US 100 101 102. G  
S: Advertising, marketing and promotional services related to all industries 
for the purpose of facilitating networking and socializing opportunities for 
business purposes; Providing on-line computer databases and on-line searchable 
databases in the field of professional networking



  was:
I conducted a US Trademark Search, this shows no results for Wookie:

http://www.trademarkia.com/trademarks-search.aspx?tn=wookiefs=01/01/1960fe=08/02/2012pri=009gs=cn=st=1

I searched at Trademarkia. This showed 3 results for Wookie, 2 were ABANDONED 
and 1 was CANCELLED. None were software-related (action figures, flavoured 
nuts, canteen services).


 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)

[
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Scott Wilson updated PODLINGNAMESEARCH-13:
--

Evidence Of Use On World Wide Web:
A Google search for Wookie Software shows Apache Wookie as the top 3 results;
the 4th result is a reference in a course description to Wookie as a
software simulator for Windows that can simulate the function of a real 68HC11
microcontroller (http://www.ele.uri.edu/courses/ele205/Lab03.pdf). Further
searches show references in a few other electronics course descriptions, as
recently as 2009.

Much further into the results is a reference to WookieChat - and IRC client for
the AmigaOS:
http://wookiechat.amigarevolution.com/wookiechat/

There are also some references to a radio-related application on some forums,
e.g.:

2100-WOOKIE-LAB- Field Programmer for the MOBIUS Radio-Series (Sky Walker)
2100 portables and mobiles radio with 5/6 Tone signalizing. v.R2.01beta
SDVN4274A.

Is dus Wookie lab software, is een Beta en daarom is hij niet volledig 100%
betrouwbaar. Dat uit zich in het soms niet kunnen benaderen van de tuningmodus.
Wookie wil bij het opslaan van je codeplug nog wel eens alle kanalen op
eenzelfde frequentie zetten. Soms kun je met een nieuwe installatie wel in de
tuningmodus komen. Maar de beste oplossing om dit uit te laten voeren door
iemand met kennis van zaken (en die gebruikt de Ms-Dos RSS versie!).

http://www.scannerforum.nl/index.php?topic=6418.0

Search at Yahoo! for wookie software:

- 5 of the top 10 results were for Apache Wookie
- 1 was a reference to Software Simulator for the M68HC11
- 1 was a wookie name generator
- 3 were torrent sites relating to an MP3 track called wookie wookie

was:
A Google search for Wookie Software shows Apache Wookie as the top 3 results;
the 4th result is a reference in a course description to Wookie as a
software simulator for Windows that can simulate the function of a real 68HC11
microcontroller (http://www.ele.uri.edu/courses/ele205/Lab03.pdf). Further
searches show references in a few other electronics course descriptions, as
recently as 2009.

Much further into the results is a reference to WookieChat - and IRC client for
the AmigaOS:
http://wookiechat.amigarevolution.com/wookiechat/

There are also some references to a radio-related application on some forums,
e.g.:

2100-WOOKIE-LAB- Field Programmer for the MOBIUS Radio-Series (Sky Walker)
2100 portables and mobiles radio with 5/6 Tone signalizing. v.R2.01beta
SDVN4274A.

http://www.scannerforum.nl/index.php?topic=6418.0

Establish whether Apache Wookie is a suitable name

Key: PODLINGNAMESEARCH-13
URL:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
Project: Podling Suitable Names Search
Issue Type: Suitable Name Search
Reporter: Scott Wilson

We have to do some investigations to ensure that Apache Wookie is a
suitable name for a TLP.
Here are some resources related to this issue:
http://incubator.apache.org/guides/names.html
http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)

[
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Scott Wilson updated PODLINGNAMESEARCH-13:
--

Much further into the results is a reference to WookieChat - and IRC client for
the AmigaOS:
http://wookiechat.amigarevolution.com/wookiechat/

There are also some references to a radio-related application on some forums,
e.g.:

2100-WOOKIE-LAB- Field Programmer for the MOBIUS Radio-Series (Sky Walker)
2100 portables and mobiles radio with 5/6 Tone signalizing. v.R2.01beta
SDVN4274A.

http://www.scannerforum.nl/index.php?topic=6418.0

Search at Yahoo! for wookie software:

- 5 of the top 10 results (including top result) were for Apache Wookie
- 1 was a reference to Software Simulator for the M68HC11
- 1 was a wookie name generator
- 3 were torrent sites relating to an MP3 track called wookie wookie

Search at Bing for wookie software:

- 2 of the top 10 results (including top result) were for Apache Wookie
- 2 were due to posts on software forums by a user called wookie
- 1 was due to a BBS sysop called The Wookie
- 3 referred to the Wookie radio frequency software identified above.
- 2 referred to the 68HC11 microprocessor emulator

Much further into the results is a reference to WookieChat - and IRC client for
the AmigaOS:
http://wookiechat.amigarevolution.com/wookiechat/

There are also some references to a radio-related application on some forums,
e.g.:

2100-WOOKIE-LAB- Field Programmer for the MOBIUS Radio-Series (Sky Walker)
2100 portables and mobiles radio with 5/6 Tone signalizing. v.R2.01beta
SDVN4274A.

http://www.scannerforum.nl/index.php?topic=6418.0

Search at Yahoo! for wookie software:

Establish whether Apache Wookie is a suitable name

Key: PODLINGNAMESEARCH-13
URL:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
Project: Podling Suitable Names Search
Issue Type: Suitable Name Search
Reporter: Scott Wilson

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

[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)


 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Wilson updated PODLINGNAMESEARCH-13:
--

Evidence Of Open Source Adoption: 
A search on Github for Wookie yields 14 repositories: 

- 7 of these are plugins for Apache Wookie, or ports of the Apache Wookie W3C 
library jar to other platforms/languages 
- alto/wookie is a Rails plugin for exporting stats; last updated 3 years ago 
- CaioMatias/Wookie is a Flash project framework 
- BookieWookie is a link-sharing plugin for Rails; last updated 3 years ago 
- wookie-translator is an english-to-wookie translator
- wookie-cab- is an empty project 
- wookie-cam is an empty project 
- fernandoafb/wookie is an empty project

A search on Sourceforge for Wookie yields 1 project: 

http://wookilang.sourceforge.net/; 

This is the Wooki Language Interpreter project (wookilang) 

This project was registered on SourceForge.net on Apr 17, 2011, and is 
described by the project team as follows: 

It is a language and interpreter aiming to test data structures, with debugging 
tools.


A search for Wookie projects at http://www.ohloh.net/ yields 12 results in 
the following order:

- Apache Wookie
- Wookie-Army [no code, and no description]
- spreadthesource's wooki [Wooki* is a smart tool to write documents. It let 
you publish them and get reviews.]
- JabberWookie Jabber Library for Java [Yet another Jabber library, written in 
Java (to the 1.1 spec). The goal of which is to be as simple to use and 
understand as possible. (Depends on the SSTTR Java Library).]
- Apache Rave 
- groovy-option-parser [the term wookie turns up in its description as an 
example of a parameter name]
- wookiesareback [wookies threading project]
- Rave in Context [The Rave in Context project develops progressively 
enhanced, usable, accessible, learnable and adaptable W3C widget templates and 
widgets that can be used for Apache Wookie and Apache Rave (both Incubating)]
- Wooky [Wooky is a free tile map editor for the creation of tile based 
games.]
- Jiss [A simulator for the M68HC11 microcontroller written in Java, based on 
the Wookie HC11 Simulator sources.]
- maroon-harvest [Like Star Wars, But With Salukis Instead of Wookies]
- quote-unquote [A quote database (QDB) engine using the CakePHP framework and 
an SQL database. This code is very close to the version powering the Wookiee' 
QDB, and was originally custom-written for that site]


  was:
A search on Github for Wookie yields 14 repositories: 

- 7 of these are plugins for Apache Wookie, or ports of the Apache Wookie W3C 
library jar to other platforms/languages 
- alto/wookie is a Rails plugin for exporting stats; last updated 3 years ago 
- CaioMatias/Wookie is a Flash project framework 
- BookieWookie is a link-sharing plugin for Rails; last updated 3 years ago 
- wookie-translator is an english-to-wookie translator (probably a 
misspelling of Wookiee from Star Wars) 
- wookie-cab- is an empty project 
- wookie-cam is an empty project 
- fernandoafb/wookie is an empty project

A search on Sourceforge for Wookie yields 1 project: 

http://wookilang.sourceforge.net/; 

This is the Wooki Language Interpreter project (wookilang) 

This project was registered on SourceForge.net on Apr 17, 2011, and is 
described by the project team as follows: 

It is a language and interpreter aiming to test data structures, with debugging 
tools.


A search for Wookie projects at http://www.ohloh.net/ yields 12 results in 
the following order:

- Apache Wookie
- Wookie-Army [no code, and no description]
- spreadthesource's wooki [Wooki* is a smart tool to write documents. It let 
you publish them and get reviews.]
- JabberWookie Jabber Library for Java [Yet another Jabber library, written in 
Java (to the 1.1 spec). The goal of which is to be as simple to use and 
understand as possible. (Depends on the SSTTR Java Library).]
- Apache Rave [depends on Apache Wookie]
- groovy-option-parser [the term wookie turns up in its description as an 
example of a parameter name]
- wookiesareback [wookies threading project]
- Rave in Context [depends on Apache Wookie]
- Wooky [Wooky is a free tile map editor for the creation of tile based 
games.]
- Jiss [A simulator for the M68HC11 microcontroller written in Java, based on 
the Wookie HC11 Simulator sources.]
- maroon-harvest [Like Star Wars, But With Salukis Instead of Wookies]
- quote-unquote [A quote database (QDB) engine using the CakePHP framework and 
an SQL database. This code is very close to the version powering the Wookiee' 
QDB, and was originally custom-written for that site]



Removed any speculation/interpretation from descriptions

 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse

[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-10-07 Thread Scott Wilson (JIRA)


[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471304#comment-13471304
 ] 

Scott Wilson commented on PODLINGNAMESEARCH-13:
---

Searched http://oami.europa.eu/ows/rw/pages/index.en.do for wookie - no 
results.

 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Podling name search - how do I contact the trademark team?

2012-10-07 Thread Scott Wilson

I've finished updating the Wookie podling name search ticket[1] with the 
results of various searches I've conducted.

Reading the guidance page[2], it states:

Once the information is collected and collated, then ask the trademark team to 
help interpret and analyse these results on the private lists, copying in the 
PPMC.

One question -  how do I do this? I can't find any mention of a mailing list 
name to send the request to.

[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
[2] http://incubator.apache.org/guides/names.html
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Ripple Emulator

2012-10-05 Thread Scott Wilson

Hey Dan,

Fantastic proposal - it will be great to see Ripple at ASF alongside Cordova, 
Wookie and DeviceMap.

S


On 5 Oct 2012, at 20:28, Dan Silivestru wrote:

 Dear Member of ASF,
 
 We are putting forward a proposal to have the Ripple Emulator project
 donated to the ASF as Top Level Project. The project is currently open
 source and can be found here: https://github.com/blackberry/Ripple-UI/
 
 Please find the proposal below (the proposal can also be found here:
 https://github.com/gtanner/ripple.apache.proposal)
 
 Ripple, A Mobile Environment Emulator
 =
 
 Abstract
 
 
 Ripple is a browser based mobile phone emulator designed to aid in the
 development
 of HTML5 based mobile applications.  Ripple is a cross platform and cross
 runtime testing/debugging tool. It currently supports such runtimes as
 Cordova, WebWorks
 and the Mobile Web.
 
 Proposal
 
 
 Ripple is going to be (in some circles already is) the goto emulator
 for rapid development of mobile web applications. This
 will be accomplished by quickly keeping up with the mobile web
 platforms as they arise (Cordova, Tizen, WAC, WebWorks, etc).
 
 Background
 ==
 
 Ripple started as a product of tinyHippos and was aquired by Research
 in Motion in late March 2011.  Ripple was then open sourced
 under the Apache 2.0 License and hosted on the blackberry github
 account (http://github.com/blackberry/Ripple-UI).
 
 Ripple is a browser based mobile phone emulator that runs as a chrome
 extension.  It fills the gap for developers between
 developing on their desktops/laptops and having to test on platform
 specific emulators or physical devices. Ripple allows develors
 to quickly edit-refresh-test in Chrome on their desktops/laptops while
 working on web content that will be embedded and distributed
 as a native application.
 
 Rationale
 =
 
 The project is currently opensourced and managed by a small team at
 Research in Motion.  We are starting to have some
 more community engagement but the project could benefit from greater
 exposure in the open source cummunity.  Our team
 overlaps highly with the Cordova group. Watching the success for that
 project in Apache has inspired us to contribute
 Ripple to the ASF as well.
 
 Ripple fills a large gap in the toolset for most mobile web developers
 between development on the desktop and testing
 on the physical device.
 
 Current Status
 ==
 
 Currently all development is managed on github via the issues and the
 direction of the project is strongly influenced by
 Research in Motion.  A more clear project plan and more open
 communication will be needed by this project to abide by
 the apache guidelines.
 
 Metriocracy
 ===
 
 Ripple has been very accepting of letting in patches from 3rd party
 developers and has been functioning like apache in requiring a CLA
 for code to be pulled in. The core team is hoping to grow and include more
 developers.
 
 Community
 =
 
 The development community of Ripple is a small but tight knit group but
 the users of the project number more than 40,000. With the launch
 ofemulate.phonegap.com (which is a portal for installing ripple) we
 are
 getting approx 5000 hits a day to that site.
 
 
 Core Developers
 ===
 
 See Inital Committers below.
 
 Alignment
 =
 
 Apache is a good match for this project due to it's close ties
 to the Cordova Project. Cordova has been very successful as a project
 since joining Apache and we hope Ripple will follow suit.
 
 Known Risks
 ===
 
 Orphaned Products
 -
 
 Ripple is a core component to the toolset at RIM and the Cordova /
 Phonegap community has embrased ripple into their tooling
 as well. This project has been under active development for 3 years
 and a lot of vested interest from both RIM and the
 community is already present to keep the tool up to date.
 
 Inexperience with Open Source
 -
 
 Ripple has been opensourced at RIM for the last year.  All of the work
 is done in the open. There are a few extra measures we need to learn
 how to take (mailing lists, project planning) for working within the
 ASF community.
 However the team has a good understanding of what needs to happen, as
 some of the
 team are also contributers to the Apache Cordova Incubator project.
 
 Homogenous Developers
 --
 
 Ripple's core team currently all works at RIM with contributions for
 some features done by third parties.  There is a
 backlog of features currently done / being put in by third parties
 such as Adobe and IBM.
 
 Reliance on Salaried Developers
 ---
 
 Most of the developers are paid by their employer to contribute to
 this project but are all highly involved on a personal
 level with this project as well as the mobile web community.
 
 Relationships with Other Apache Products

Graduate with blocked release?

2012-10-03 Thread Scott Wilson

We recently started the process of taking Wookie to graduation, however the 
current Wookie release is blocked pending the resolution of a crypto export 
issue [1].  

My question is: can we proceed with graduation - hopefully presenting a 
resolution at the next meeting -  without first resolving this issue?

Cheers,

- Scott

[1]  https://issues.apache.org/jira/browse/LEGAL-148
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-08-23 Thread Scott Wilson (JIRA)

Scott Wilson created PODLINGNAMESEARCH-13:
-

 Summary: Establish whether Apache Wookie is a suitable name
 Key: PODLINGNAMESEARCH-13
 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson


We have to do some investigations to ensure that Apache Wookie is a suitable 
name for a TLP. 

Here are some resources related to this issue: 

http://incubator.apache.org/guides/names.html 
http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-08-23 Thread Scott Wilson (JIRA)


 [ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Wilson updated PODLINGNAMESEARCH-13:
--

Evidence Of Registration: 
I conducted a US Trademark Search, this shows no results for Wookie:

http://www.trademarkia.com/trademarks-search.aspx?tn=wookiefs=01/01/1960fe=08/02/2012pri=009gs=cn=st=1

 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-08-23 Thread Scott Wilson (JIRA)


[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440198#comment-13440198
 ] 

Scott Wilson commented on PODLINGNAMESEARCH-13:
---

A Google search for Wookie Software shows Apache Wookie as the top 3 results; 
the 4th result is a reference in a course description to Wookie as a 
software simulator for Windows that can simulate the function of a real 68HC11 
microcontroller (http://www.ele.uri.edu/courses/ele205/Lab03.pdf). Further 
searches show references in a few other electronics course descriptions, as 
recently as 2009.

Much further into the results is a reference to WookieChat - and IRC client for 
the AmigaOS:
http://wookiechat.amigarevolution.com/wookiechat/

There are also some references to a radio-related application on some forums, 
e.g.:

2100-WOOKIE-LAB- Field Programmer for the MOBIUS Radio-Series (Sky Walker) 
2100 portables and mobiles radio with 5/6 Tone signalizing. v.R2.01beta 
SDVN4274A. 

Is dus Wookie lab software, is een Beta en daarom is hij niet volledig 100% 
betrouwbaar. Dat uit zich in het soms niet kunnen benaderen van de tuningmodus. 
Wookie wil bij het opslaan van je codeplug nog wel eens alle kanalen op 
eenzelfde frequentie zetten. Soms kun je met een nieuwe installatie wel in de 
tuningmodus komen. Maar de beste oplossing om dit uit te laten voeren door 
iemand met kennis van zaken (en die gebruikt de Ms-Dos RSS versie!).

http://www.scannerforum.nl/index.php?topic=6418.0


 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-08-23 Thread Scott Wilson (JIRA)


[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440203#comment-13440203
 ] 

Scott Wilson commented on PODLINGNAMESEARCH-13:
---

A search on Github for Wookie yields 14 repositories:

- 7 of these are plugins for Apache Wookie, or ports of the Apache Wookie W3C 
library jar to other platforms/languages
- alto/wookie is a Rails plugin for exporting stats; last updated 3 years ago
- CaioMatias/Wookie is a Flash project framework
- BookieWookie is a link-sharing plugin for Rails; last updated 3 years ago
- wookie-translator is an english-to-wookie translator (probably a 
misspelling of Wookiee from Star Wars)
- wookie-cab- is an empty project
- wookie-cam is an empty project
- fernandoafb/wookie is an empty project

 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name

2012-08-23 Thread Scott Wilson (JIRA)


[ 
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440206#comment-13440206
 ] 

Scott Wilson commented on PODLINGNAMESEARCH-13:
---

A search on Sourceforge for Wookie yields 1 project:

http://wookilang.sourceforge.net/;

This is the Wooki Language Interpreter project (wookilang)

This project was registered on SourceForge.net on Apr 17, 2011, and is 
described by the project team as follows:

It is a language and interpreter aiming to test data structures, with debugging 
tools.

 Establish whether Apache Wookie is a suitable name
 

 Key: PODLINGNAMESEARCH-13
 URL: 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13
 Project: Podling Suitable Names Search
  Issue Type: Suitable Name Search
Reporter: Scott Wilson

 We have to do some investigations to ensure that Apache Wookie is a 
 suitable name for a TLP. 
 Here are some resources related to this issue: 
 http://incubator.apache.org/guides/names.html 
 http://www.apache.org/foundation/marks/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



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

[RESULT] [VOTE] Release Apache Wookie 0.10.0-incubating (General Incubation List)

2012-05-24 Thread Scott Wilson

The 72 hour voting period has passed and the vote is now closed. Thanks to 
everyone who took time to review the release. 

With the three IPMC member votes (3 of them mentors) and 3 PPMC votes the vote 
succeeds

IPMC Member voting record:

* Ate Douma: +1
* Ross Gardler +1
* Matt Franklin +1

* Denotes an IPMC member vote cast on the wookie-dev list.

Thanks,

Scott.

On 21 May 2012, at 16:13, Scott Wilson wrote:

 This is the third incubator release for Apache Wookie, with the artifacts
 being versioned as 0.10.0-incubating.
 
 We are requesting a lazy consensus vote, as we have already received 3
 binding IPMC +1 votes during the release voting on wookie-dev -
 
 Vote thread:
 http://markmail.org/message/2p4veen6n22w7hnb
 
 Result:
 http://markmail.org/message/d2jzbrdgic3od5uj
 
 Svn source tag:
 https://svn.apache.org/repos/asf/incubator/wookie/tags/0.10.0-incubating/
 
 Release notes:
 https://svn.apache.org/repos/asf/incubator/wookie/tags/0.10.0-incubating/RELEASE_NOTES
 
 Release artifacts:
 http://people.apache.org/builds/incubator/wookie/0.10.0-incubating/
 
 Maven artifacts
 https://repository.apache.org/content/repositories/orgapachewookie-094/
 
 PGP release keys:
 https://svn.apache.org/repos/asf/incubator/wookie/KEYS
 
 Lazy consensus, vote open for 72 hours.
 
 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why) 
 
 


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

Re: Wink status (Was: Shepherds for podling reports)

2012-05-09 Thread Scott Wilson


On 9 May 2012, at 17:23, Luciano Resende wrote:

 On Wed, May 9, 2012 at 9:15 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi,
 
 Thanks for the report, Wink, and for the review, Dave!
 
 On Fri, May 4, 2012 at 9:33 PM, Dave Fisher dave2w...@comcast.net wrote:
 From activity it looks like this project should have graduated into a TLP a 
 year
 ago. It looks like a mature and well developed project. I don't understand 
 why
 they think that they should become a subproject of Geronimo or Tuscany.
 They are a mature and useful tool. It's time for this bird to fly on its own
 wings. They are an example of a small, viable community that contributes
 to more than one other community. Podling Namesearch and graduation
 should be next.
 
 Wink, any thoughts on this?
 
 BR,
 
 Jukka Zitting
 
 
 +1, This is my opinion as well, but we started considering other
 options mainly because of some feedback we got on the last discussion
 on the Wink mailing list (see summary on February board report).
 
 If the IPMC thinks otherwise and would be ok with the Wink project
 graduation based on a small, viable community that contributes to
 more than one other community I'm more then happy to continue the
 Graduation process.
 


+1  I've used Wink and its a great project - I think it should be a TLP in its 
own right rather than a subproject as being a standalone, relatively simple 
framework rather than part of a great big stack is one of its selling points 
(for me at least)

 
 [1] http://wiki.apache.org/incubator/February2012
 
 -- 
 Luciano Resende
 http://people.apache.org/~lresende
 http://twitter.com/lresende1975
 http://lresende.blogspot.com/
 
 -
 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: TL;DR

2012-02-03 Thread Scott Wilson

On 3 Feb 2012, at 23:17, Benson Margulies wrote:

 A number of people are asking for the incubator PMC to take a deep
 breath and allow room to digest and contemplate the various issues
 that have led to a bumper crop of email. These are complex questions,
 and even if we could avoid intemperate exchanges, there is still going
 to be a lot to read and think about.

+1

I'm a committer on 3 incubator projects, so I have quite a lot of ASF-related 
email already. I don't understand most of the points being discussed on the 
general list as I don't really have time to read and make sense of it all.

The incubator doesn't feel particularly broken and in need of fixing at my 
level of engagement, so most of the tone of the conversation does little other 
than give me a nagging worry that I'm missing something important that might 
affect the projects I work on. 

I expect many more on this list will just filter these discussions out and 
trust everyone concerned to do whats sensible.

So, slow down please, there's no need to rush.

 
 One way to make the load lighter is to try to make one decision at a
 time. Entirely selfishly, I suggest looking at the chair election
 first.

+1


 
 -
 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: Questions for projects

2012-01-31 Thread Scott Wilson

On 31 Jan 2012, at 18:17, Luciano Resende wrote:

 On Mon, Jan 30, 2012 at 9:32 AM, Jukka Zitting jukka.zitt...@gmail.com 
 wrote:
 Hi,
 
 The deadline for podlings to submit their February reports is already
 in two days since the ASF board meeting is scheduled for Feb 15th.
 
 
 Sure, but there isn't even a February page at the wiki :
 
 http://wiki.apache.org/incubator/
 
 Should one just copy from Feb 2011 ? Or is there some template that I missed ?

Its there, it just hasn't got a link from the front page:

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

 
 -- 
 Luciano Resende
 http://people.apache.org/~lresende
 http://twitter.com/lresende1975
 http://lresende.blogspot.com/
 
 -
 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] Release Apache Wookie 0.9.1-incubating RC5 (General Incubation List)

2011-11-21 Thread Scott Wilson

Bump! 

I know its been a busy month on general@incubator, but if another IPMC member 
can take the time to check out and vote on this release it would be 
appreciated...

On 16 Nov 2011, at 16:05, Ross Gardler wrote:

 +1
 We still need another IPMC vote.
 
 
 On 14 November 2011 19:03, Paul Sharples p.sharp...@bolton.ac.uk wrote:
 We have already received 1 IPMC +1 vote (plus an additional 3 PPMC +1 votes)
 during the release voting on wookie-dev. (We need two more IPMC votes)
 
 Vote thread:
 http://incubator.markmail.org/search/?q=wookie-dev#query:wookie-dev%20date%3A20%20+page:1+mid:vp4l3b44gqonew2t+state:results
 
 Result:
 http://incubator.markmail.org/search/?q=wookie-dev#query:wookie-dev%20date%3A20%20+page:1+mid:5sjpdaify3xbxtle+state:results
 
 Svn source tag:
 https://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.1-incubating/
 
 Release notes:
 https://svn.apache.org/repos/asf/incubator/wookie/tags/0.9.1-incubating/RELEASE_NOTES
 
 Release artifacts:
 http://people.apache.org/~psharples/wookie/staging-area/0p9p1/rc5/
 
 Maven artifacts
 https://repository.apache.org/content/repositories/orgapachewookie-165/
 
 PGP release keys:
 https://svn.apache.org/repos/asf/incubator/wookie/KEYS
 
 Vote open for 72 hours.
 
 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)
 
 
 
 
 
 -- 
 Ross Gardler (@rgardler)
 Programme Leader (Open Development)
 OpenDirective http://opendirective.com
 
 -
 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 Apache Callback for incubation

2011-10-12 Thread Scott Wilson

+1 (non-binding)

On 11 Oct 2011, at 22:09, Jukka Zitting wrote:

 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 common

Re: [PROPOSAL] PhoneGap for Apache Incubator

2011-10-01 Thread Scott Wilson

Great proposal! Focus on open web and open standards is spot on.

S

On 1 Oct 2011, at 00:57, Brian LeRoux wrote:

 Hi everyone,
 
 I would like to propose PhoneGap to be an Apache Incubator project.
 (Under the new, still proposed name, Apache Callback.)
 
 Here's a link to the proposal in the current PhoneGap wiki:
 http://wiki.phonegap.com/w/page/46311152/apache-callback-proposal
 
 Thank you!
 Brian
 
 -
 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: IP Clearance - transferral or licensing of copyright ownership?

2011-09-22 Thread Scott Wilson


On 22 Sep 2011, at 11:20, Robert Burrell Donkin wrote:

 Hi Sander
 
 I'm glad you asked these questions here: asking well researched
 questions is the best way to improve our process and documentation
 
 but just for the record, the legal-discuss list[1] is the right place
 for projects to ask almost all questions about copyright (being
 public, it's not appropriate for some sensitive issues)
 
 On Wed, Sep 21, 2011 at 10:27 AM, Sander van der Waal
 sander.vanderw...@oucs.ox.ac.uk wrote:
 I'm trying to get my head around the IP clearance process and
 specifically about what happens to the copyright ownership during that
 process. Although IP clearance gets discussed once in a while on this
 list I couldn't find a clear answer in the archives on this specific
 point.
 
 In general Apache prefers to license with no change copyright ownership.
 
 When a project with a pre-existing code base joins the incubator, does
 the copyright of that code base get transferred to the ASF or will it be
 licensed to the ASF?
 
 Almost always through a license
 
 Reading through the IP clearance guide [1], it mentions the Software
 Grant Agreement (SGA) and going to the text [2] it states that it is a
 License Agreement to grant a license to the ASF. Also the CCLA [3] and
 the ICLA [4] are license agreements. I interpret that to mean that the
 copyright ownership remains with the licensor and only a license is
 granted.
 
 That is my understanding
 
 IMHO an explicit explanation of these point would improve the
 documentation. It'd be great if someone contributed an improved
 version :-)
 
 On the other hand, the ASF general FAQ states that the copyright of ASF
 projects is owned by the ASF, more specifically The members own the
 code [5].
 
 It is the collective copyright that is owned by Apache
 
 Projects are composed by a selection process undertaken by the PMC
 from a variety of contributions. Each contributor owns the copyright
 in their patch but the creative act of composition entitles Apache to
 claim collective copyright for the final work. This collective
 copyright claim is noted in the NOTICE. The header for each document
 should acknowledge that Apache has licensed (from the original
 contributions) the rights required to offer the document to the public
 under the Apache License, Version 2 but almost always will not contain
 a copyright claim.
 
 If the documentation is missing this explanation then it'd be great if
 someone contributed an improved version :-)


This is a really good explanation - thanks Robert!  I'd been wondering the same 
thing as Sander.

 
 Also the IP Clearance template [6] has a check that says
 Check and make sure that the papers that transfer rights to the ASF
 been received. But it seems that the SGA and *CLAs are just license
 agreements and don't include a transferral of rights? I must be missing
 something obvious here but I'm not sure what.
 
 Copyright licenses grants the licensee rights otherwise restricted by
 copyright law. Transfer might be taken to mean exclusive so
 assign would be a better choice.
 
 But this could be phrased more more clearly and explained explicitly.
 It'd be great if someone contributed an improved version :-)
 
 Going through a few NOTICE files of projects doesn't really make it
 clearer, because some only specify the ASF as copyright owner and others
 specify in general terms that it includes software [originally]
 developed at X.
 
 The standard NOTICE should include note both the collective copyright
 and that Apache developed the software
 
 I know copyright ownership might not be a big deal to many here, but we
 are dealing with many open source projects where the project lead has
 a very strong sense of ownership over the code. Besides educating them
 about the issues I want to make sure I get the facts right.
 
 Thanks for taking the time to frame good questions :-)
 
 The documentation here in the Incubator is developed by the community
 for the community. The best podlings change the Incubator more than
 the Incubation process changes them. Karma is earned here at Apache
 through contribution.
 
 The documentation needs improvement in this area. I'd be glad to
 review patches and work with anyone would could find some cycles to
 contribute. Anyone want to start by diving in with suggestions?
 
 Robert
 
 [1] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/
 
 -
 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] S4 for the Apache Incubator

2011-09-15 Thread Scott Wilson

On 14 Sep 2011, at 21:19, Leo Neumeyer wrote:

 Dear all,
 
 I would like to propose S4 to be an Apache Incubator project.  S4 is a
 distributed streaming platform written in Java.
 
 Here is a link to the proposal in the Incubator wiki:
 http://wiki.apache.org/incubator/S4Proposal
 
 Thanks,
 Leo Neumeyer
 
 http://s4.io
 http://twitter.com/leoneu


This sounds like a really interesting proposal Leo - would it work with 
emerging streaming capabilities for browser such as WebRTC and WebSockets? For 
example, would it work as a processor for streams coming in from a browser via 
WebRTC or HTML5 Device Capture, as well as for pushing streams out into video 
elements or to websocket clients?

 
 -
 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 OpenOffice.org for incubation

2011-06-11 Thread Scott Wilson

+1 (non-binding)

/-/-/-/-/-/
Scott Wilson

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

Re: OO.o and web widgets

2011-06-05 Thread Scott Wilson


On 5 Jun 2011, at 09:09, Ross Gardler wrote:

 Sent from my mobile device (so please excuse typos)
 
 On 4 Jun 2011, at 23:31, robert_w...@us.ibm.com wrote:
 
 For 
 example, with Lotus Symphony we've added a mechanism to integrate web 
 widgets. 
 
 I'd like to know a little more about this. 
 
 What are web widgets in this context? Does Lotus Symphony use either of the 
 two common web widgets standards W3C Widgets or OpenSocial Gadgets?
 
 If so (or if there is interest in doing so) the Apache Wookie and Rave (both 
 incubating) and Apache Shindig may be relevant. 

I saw an internal demo by one of our partners that used W3C Widgets integrated 
in Powerpoint; this would be a great feature for OOo presentations too.

 
 Ross
 
 -
 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 Rave into the Incubator

2011-02-25 Thread Scott Wilson

 offered by The MITRE Corporation is already open source and Apache 
 Licensed.
 
 
  SURFnet SURFConext Portal 
 
 This source will be brought into the Incubator as SURFnets contribution; 
 initial project members have already been given access for evaluation 
 purposes.
 
 
  Open Gateway Computing Environments 
 
 The OGCE will contribute its Gadget Container code, which is Apache licensed 
 and available from !SourceForge, with current dependencies and their licenses 
 described below.
 Other OGCE software efforts are not covered by this incubator proposal and 
 are not included in the code contribution.
 
 
 == Dependencies on other Apache Projects ==
 
 * Apache Shindig
 * Apache Tomcat
 * Apache Tiles
 * Apache !HttpComponents
 * Apache Commons
 * Apache Log4J
 * Apache Maven
 * Apache Ant
 
 
 == Cryptography ==
 
 There is no cryptography in the code at this time.
 
 OGCE has requirements to support security for Computational Grids and Clouds. 
 Although the code will not have any cryptographic implementations, in the 
 future there will be dependencies on external cryptographic libraries. Before 
 committing any cryptographic dependencies, the process listed at 
 http://www.apache.org/dev/crypto.html will be followed.
 
 
 == Required Resources ==
 
 
 === Mailing lists ===
 
 * rave-dev
 * rave-commits
 * rave-private (moderated subscriptions)
 
 
 === Subversion Directory ===
 
 * http://svn.apache.org/repos/asf/incubator/rave
 
 
 === Issue Tracking ===
 
 We intend to make use of Jira for issue tracking.
 
 Proposed JIRA key: JIRA-RAVE
 
 
 === Other Resources ===
 
 None right now.
 
 
 == Initial Committers ==
 
 Names of initial committers with affiliation and current ASF status:
 * Ate Douma (Hippo), Apache Member, id: ate
 * Unico Hommes (Hippo), Apache Committer, id: unico
 * Ard Schrijvers (Hippo), Apache Committer, id: ard
 * Woonsan Ko (Hippo), Apache Committer, id: woonsan
 * Matt Franklin (MITRE, osec)
 * Jesse Ciancetta (MITRE, osec)
 * Tony Carlucci (MITRE, osec)
 * Ross Gardler (OSS Watch), Apache Member, id: rgardler
 * Sander van der Waal (OSS Watch)
 * Scott Wilson (University of Bolton), Apache Committer, id: scottbw
 * Hadrian Zbarcea (independent), Apache Member, id: hadrian
 * Marlon Pierce (Pervasive Technology Institute Indiana University, OGCE)
 * Raminderjeet Singh (Pervasive Technology Institute Indiana University, OGCE)
 * Zhenhua Guo (Pervasive Technology Institute Indiana University, OGCE)
 * Suresh Marrunbsp;(Pervasive Technology Institute Indiana University, OGCE)
 * Niels van Dijk (SURFNET, SURFConext)
 * Maarten Kremers (SURFNET, SURFConext)
 * Bas Zoetekouw (SURFNET, SURFConext)
 * Joost van Dijk (SURFNET, SURFConext)
 * Okke Harsta (Zilverline, SURFConext)
 
 
 == Sponsors ==
 
 
 === Champion ===
 
 * Ate Douma
 
 
 === Nominated Mentors ===
 
 * Ate Douma
 * Sylvain Wallez
 * Upayavira
 * Ross Gardler
 * Hadrian Zbarcea
 
 
 === Sponsoring Entity ===
 
 * Apache Incubator Project
 
 
 == Appendix A: External Dependencies ==
 
 Here's the list of identified external dependencies for each of the initial 
 code contributions:
 
  MITRE OpenSocial Enterprise Container 
 
 * ''Build Time/Test Dependencies''
 
 '''Apache Licensed'''
  * Jakarta ORO
  * Apache log4j
  * cglib
  * !EasyMock
  * Google Guice
  * h2datasource (MITRE Developed)
  * Objenesis
  * Spring Framework Test
  * servlet-api
 
 '''BSD Licensed'''
  * YUI Compressor
  * YUI Compressor Ant Task
  * JUnit
 
 '''MPL  EPL Licensed'''
  * H2 Database Engine
 
 '''Other Licenses'''
  * ASM: http://asm.ow2.org/license.html
  * Cobertura: http://cobertura.sourceforge.net/license.html
 
 * ''Runtime Dependencies''
 
 '''Apache Licensed'''
  * Apache Commons
  * Apache Taglibs
  * Google Collections
  * Jackson
  * Apache log4j
  * Shindig
  * Spring Framework
  * Spring Security
  * Apache Tiles
  * Google Guice
  * h2datasource (MITRE Developed)
 
 '''MPL  EPL Licensed'''
  * H2 Database Engine
 
 '''EPL Licensed'''
  * !EclipseLink
  * javax.persistence API
  * AspectJ
 
 '''BSD-style Licensed'''
  * !FreeMarker: http://freemarker.sourceforge.net/docs/app_license.html
 
 '''CDDL Licensed'''
  * JSTL
  * !JavaMail
 
 '''MIT Licensed'''
  * SLF4J
 
 '''Other Licenses'''
  * AOP Alliance: http://aopalliance.sourceforge.net/
 
  SURFnet SURFConext portal 
 
 ''Dependencies and licenses of all dependencies of the COIN portal (excluded 
 the shindig dependencies)''
 
 '''Apache Software License, Version 1.1'''
  * cglib:cglib-nodep:jar:2.2:compile
 
 '''Apache Software License, Version 2.0'''
  * org.codehaus.jackson:jackson-mapper-lgpl:jar:1.5.5:compile
  * org.springframework:spring-core:jar:3.0.3.RELEASE:compile
  * org.springframework:spring-orm:jar:3.0.3.RELEASE:compile
  * org.springframework:spring-jdbc:jar:3.0.3.RELEASE:compile
  * org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
  * org.springframework:spring-context:jar:3.0.3.RELEASE:compile

Re: [VOTE] Accept Wave into the incubator

2010-11-30 Thread Scott Wilson

[X] +1 Accept Wave for incubation

non-binding



smime.p7s
Description: S/MIME cryptographic signature

Re: Quick project submission question

2010-09-08 Thread Scott Wilson

On 8 Sep 2010, at 15:13, Carl Trieloff wrote:

 
 What is the view of having a project in Apache that pulls substantial 
 components
 that are licensed under ASL as dependencies into the code base. I.e. not 
 coping the
 code, but using components that have been built and maintained elsewhere 
 under ASL
 but used as dependencies for running.
 
 I assume this is not an issue, based in the info posted on use of licenses -- 
 however I'm
 interested in understand if others have had positive or negative experiences 
 with such
 a case.

Hi Carl,

Wookie has been using Ivy[1] to pull in external dependencies as part of the 
build process. It took a bit of initial effort to get right, but now works 
really nicely, and makes it much easier to track external libraries and check 
their licenses are compatible.  You can also distinguish between dependencies 
that are needed for development, for building, and for distribution and 
downstream reuse. There is an Eclipse plugin for Ivy that works pretty well too.

The only vaguely negative thing I found was the initial challenge of getting 
the hang of how Ivy works, but we had good help from other community members 
and from our mentors on that.

[1] http://ant.apache.org/ivy/

- Scott

 
 Carl.
 
 -
 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: Quick project submission question

2010-09-08 Thread Scott Wilson


On 8 Sep 2010, at 15:40, Carl Trieloff wrote:

 On 09/08/2010 10:29 AM, Scott Wilson wrote:
 On 8 Sep 2010, at 15:13, Carl Trieloff wrote:
 
   
 What is the view of having a project in Apache that pulls substantial 
 components
 that are licensed under ASL as dependencies into the code base. I.e. not 
 coping the
 code, but using components that have been built and maintained elsewhere 
 under ASL
 but used as dependencies for running.
 
 I assume this is not an issue, based in the info posted on use of licenses 
 -- however I'm
 interested in understand if others have had positive or negative 
 experiences with such
 a case.
 
 Hi Carl,
 
 Wookie has been using Ivy[1] to pull in external dependencies as part of the 
 build process. It took a bit of initial effort to get right, but now works 
 really nicely, and makes it much easier to track external libraries and 
 check their licenses are compatible.  You can also distinguish between 
 dependencies that are needed for development, for building, and for 
 distribution and downstream reuse. There is an Eclipse plugin for Ivy that 
 works pretty well too.
 
 The only vaguely negative thing I found was the initial challenge of getting 
 the hang of how Ivy works, but we had good help from other community members 
 and from our mentors on that.
 
 [1] http://ant.apache.org/ivy/
 
 - Scott
 
   
 
 Scott,
 
 Do you see any negative sides from the community perspective with the 
 dependencies that or from projects
 outside of Apache?
 
 Carl.

I think it depends on the nature of the project you depend on. For the most 
part these are pretty mature, commonly used libraries. 

However in one case we did have the issue that we had a problem that was caused 
by a bug in a dependency (HtmlCleaner) where it wasn't very clear from the 
website whether the project was still active (patches not applied, no recent 
commits etc). In the end I just asked nicely on their tracker if it could be 
fixed, waited patiently, and eventually it was :-) 

I can imagine there might be problems if you got into a blame game with 
upstream projects, or where there is a combination of a big culture difference 
plus an unstable codebase. I think the answer is to evaluate dependencies from 
a community and sustainability viewpoint, not just a functional one.

 -
 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: Resigning as Wookie Mentor

2010-08-18 Thread Scott Wilson

Hi Gav,

You've done a heck of a lot more than sort out license headers! In particular 
when we first entered the incubator there were so many things you did to help 
us get our act together.

So thanks for all your help and input as a Wookie mentor, I really appreciate 
all that you've done for us.

S


On 18 Aug 2010, at 01:02, Gav... wrote:

 Hi All,
 
 I am a passive Mentor, one that jumps in and says or does something when and
 if required.
 
 I've sorted a fair few license header issues with RAT here at Wookie, some
 are still to be resolved btw,
 but otherwise their hasn't been much for me to do.

 
 I had a more hands on role where needed for Log4PHP until it graduated, and
 with Libcloud I
 again take a more passive approach as there really isn't much for me to do.
 With LibCloud that
 will change as I gear up towards moving them out in the next 3 months or so.
 
 With all the talk currently about what a Mentor should or should not be on
 the Incubator lists, 
 with lots of folks looking at 'active mentors' being the favoured option, I
 would like to resign
 as Mentor for the Wookie podling effective immediately.
 
 Wookie has other capable Mentors who are more 'active' and so should not
 affect the direction 
 of the Wookie project in any way.
 
 You lose a Incubator PMC member vote of course, but that is not what it
 means to be active and I
 feel uncomfortable being a Mentor purely to be an extra vote.
 
 Gav...
 
 
 


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

Re: Interest in Android-based projects?

2010-02-16 Thread Scott Wilson



On 16 Feb 2010, at 10:05, Nick Kew wrote:



On 15 Feb 2010, at 21:03, Christopher Brind wrote:

I dare say I would probably be interested in most anything you can  
come up
with :) but I suspect the project would need to be something more  
specific

as a starter for the incubator?


+1 to that.

What sets android apart from its peers to make it more deserving of
apache's attention?  It's not even the most open of mobile platforms!

Something I could be interested in is a lab for cross-platform
mobile development.  But I don't have a proposal that would
work as an apache project.


I completely agree - what I think would be useful would be a W3C  
Widgets[1]  W3C DAP[2] implementation for Android to enable cross- 
platform standards-based mobile app development (as suggested by Peter- 
Paul Koch [3]). Apache Wookie(Incubating)[4] already implements the  
Widgets spec so there is code there to build on.


[1] http://www.w3.org/TR/widgets/
[2] http://www.w3.org/2009/dap/
[3] http://quirksmode.org/presentations/sf09/google.pdf
[4] http://incubator.apache.org/wookie/


--
Nick Kew

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





smime.p7s
Description: S/MIME cryptographic signature

Re: Google Wave - anyone?

2009-07-30 Thread Scott Wilson

Yes, Wookie is a server-side Widget repository and runtime/state  
management application that implements the Google Wave Gadget APIs; it  
has an API for connecting to applications that manage participants and  
contexts, which can include waves but also traditional CMS and  
intranet groups etc. So it could plug into a Wave Server (c) to handle  
the gadget management task.


S

On 30 Jul 2009, at 06:55, Bernd Fondermann wrote:


On Wed, Jul 29, 2009 at 15:58, Scott
Wilsonscott.bradley.wil...@gmail.com wrote:
Wookie implements the Wave Gadget API, which is one part of a  
Google Wave

system, but not the Wave Protocol itself.

It might be interesting if Vysper could make use of Wookie for the  
wave

gadgets part.


Is Wookie a server-side technology? Otherwise I don't see the link
between both.
Maybe it could be the other way round (Wookie using Vysper), if Wookie
makes use of the XMPP protocol.

Of course, when it comes to implementing Wave, all projects should  
join efforts.


Here is a short wrap-up of what you need to implement Wave:
+ a Wave client - this is a very fat client, and it's also a XMPP  
client

+ a server-side Wave Provider, consisting of
 (a.) Network Server(s)
 (b.) Wave Store
 (c.) Wave Server

In this setup, I'd see (a.) as a XMPP server running the Wave Protocol
(an extension of XMPP), probably tunneling through HTTP[2]. Compared
to implementing XMPP, implementing the Wave protocol extension should
be relatively easy.
The hard and critical part is definitively (c.), with all the
Operational Transformation stuff going on. Google starts open sourcing
this at [1].

[1] http://code.google.com/p/wave-protocol/
[2] http://xmpp.org/extensions/xep-0124.html

  Bernd



S

On 29 Jul 2009, at 12:24, Emmanuel Lecharny wrote:


Christian Grobmeier wrote:


Hi,


Hi,


I know my request might be a bit unusual, but is somebody here
preparing an idea for implementing the Google Wave Protocol? I  
might

want to follow, if somebody does.



You may ask Bernd Fondermann about that. He has started a project  
called

Vysper (http://mina.apache.org/vysper) which is a XMPP server


--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.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





smime.p7s
Description: S/MIME cryptographic signature

Re: Google Wave - anyone?

2009-07-29 Thread Scott Wilson

Wookie implements the Wave Gadget API, which is one part of a Google  
Wave system, but not the Wave Protocol itself.


It might be interesting if Vysper could make use of Wookie for the  
wave gadgets part.


S

On 29 Jul 2009, at 12:24, Emmanuel Lecharny wrote:


Christian Grobmeier wrote:

Hi,


Hi,

I know my request might be a bit unusual, but is somebody here
preparing an idea for implementing the Google Wave Protocol? I might
want to follow, if somebody does.



You may ask Bernd Fondermann about that. He has started a project  
called Vysper (http://mina.apache.org/vysper) which is a XMPP server



--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



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





smime.p7s
Description: S/MIME cryptographic signature

Re: Wookie IP clearance

2009-07-22 Thread Scott Wilson


On 22 Jul 2009, at 20:31, William A. Rowe, Jr. wrote:


The one thing that might be concerning is that most people will use a
query such as;

http://www.google.com/search?q=wookie+download

and be lost in the approx 135k results :)



Not quite as bad on that score as the River or Click or Ace  
projects I imagine... besides, it also sort of fits alongside Droids  
and Empire ;-)

smime.p7s
Description: S/MIME cryptographic signature

Re: Proposal for Wookie a W3C Widget/Google Wave widget engine

2009-07-08 Thread Scott Wilson


Hi Chris,

Thank you very much for your comments - as one of the initial  
committers I'll try and answer some of the items you've  raised:


1. Terminology

As we are in an area with lots of overlapping specifications I  
completely agree that we need to be careful with terminology.


2. OpenSocial Gadgets

Yes, Wookie supports OpenSocial Gadgets in exactly the way you  
describe, by pulling in the whole Shindig service to create a combined  
servlet application, exposing both the Shindig and Wookie APIs in  
full. However as a convenience we implement  in Wookie some Shindig  
features that would otherwise need to hook into another user- 
implemented backend, such as preference persistence.


You are also correct that someone implementing a Wookie server still  
needs to hook in the Shindig data interface to their social graph data  
to use OpenSocial features. We don't implement this in Wookie;  we  
deliberately keep integration with Shindig lightweight - partly as  
both projects are changing rapidly, and partly as we know users will  
want to wire together parts of the server backend in various ways and  
we don't want to obstruct that if its at all avoidable. So at this  
point I think social graph features are out of scope for Wookie, and  
delegated to Shindig. There is a new social software activity in W3C,  
however this has not identified any specifications; if this W3C group  
did develop a social graph API for Widgets then the project could  
consider whether that ought to be in scope.


I think the governance issues in this space may be a bit off-topic. I  
think however its fair to summarize that this is a complex space with  
overlapping specifications under different models of governance,  
backed by different parties and interests in different sectors, and  
application developers and users are currently caught in the middle of  
it. One of the goals of Wookie is to enable users to make use of great  
widgets/gadgets/apps  in their applications without having to worry  
about any of the backstory.


3. Wave Gadgets

I don't agree with your last point, however:

Google Wave Gadgets is a different beast entirely, they're basically  
just
the same gadgets as from OpenSocial, but without the real time Wave  
server
behind it that drives the real time data state changes it doesn't  
seem to
make a lot of sense to support it in a portal type project, and  
pulling in a
complete communications platform might be outside of Wookie's  
project scope.


The Google Wave Gadget API consists of two related JavaScript APIs:  
one for shared participants, and one for shared state. As Sylvain  
remarked these are quite simple in principle and are orthogonal to the  
spec used for the packaging and configuration of a Gadget/Widget. In  
Wookie we implemented these APIs and integrated them into support for  
W3C Widgets as an optional feature using Comet to drive state changes  
(an independent OSS Wave Server project, PygoWave, does exactly the  
same thing). This does not require pulling in a communications  
platform, and is supported out of the core architecture that Wookie  
implements for all Widgets.


There has been considerable demand for synchronous collaborative  
widgets that can be embedded in portal-like containers outside of and  
predating Google Wave; for example, several specifications were  
developed and adopted in the elearning market since 2001 to support  
just this use case, and our team defined a specification very similar  
to the Wave Gadget API in 2005 building on this prior work (this is  
why we were able to implement the Wave Gadget API in Wookie within a  
day of its announcement, the first OSS implementation of the Google  
Wave Gadget API).


As Sylvain points out, the main focus of Wookie is W3C Widgets, and so  
we implement the Wave/synchronous collaboration as a Feature extension  
(as defined in W3C Widgets PC) which is enabled for a Widget only if  
it declares it as a required feature in its config.xml file. Currently  
the code implementing the Wave Gadget API is in its own package  
(widgetservice.feature.wave) and can be built as a standalone  
extension in future builds. The technology enabling it - sibling  
widget instances and Comet - is integrated in the core engine,  
however, as other extension APIs may want to use this mechanism not  
just the Google Wave Gadgets API.


Hope this helps,

- Scott


On 6 Jul 2009, at 13:32, Chris Chabot wrote:


Hey guys,

Great looking proposal!

On Mon, Jul 6, 2009 at 1:53 PM, Ate Douma a...@douma.nu wrote:



The Wookie proposal has my high interest, especially from the  
bridging POV

between W3C Widgets and Google Gadgets.



It seems there's a few mixed terminologies here, so in interest of  
making

sure we're all talking about the same things I'll quickly go over the
different types of 'gadgets' that could potentially be supported by  
Wookie:



  - Google Gadgets, as described here:

Re: Proposal for Wookie a W3C Widget/Google Wave widget engine

2009-07-06 Thread Scott Wilson


Hi Sylvain,

I'm Scott Wilson, one of the named committers on the Wookie proposal;  
I'm also a contributor to the W3C Widgets family of specifications.


You are right in your assessment; W3C Widgets and Google Gadgets are  
indeed potential competing specifications for web widgets, despite the  
scoping statement in the W3C Landscape document that tries to make a  
hard distinction - this is more for political than technical reasons,  
as when you dig into the technology its clearer applicable in a wide  
range of environments.


Because of this we are keen to enable platform developers and widget  
developers to avoid having to make a strong choice now between Google  
and W3C, and for users to need to distinguish between widgets/gadgets  
developed for mobile, desktop or web use, or which spec its been  
written to. We've also successfully integrated the Google Wave Gadget  
API with W3C Widgets*, an example of mixing and matching Widget  
standards.


We currently embed Shindig as a component in deployments, and connect  
together the APIs where we can - for example, we implement the  
setPrefs feature of Shindig by connecting it up to our  
implementation of the W3C Preferences API (itself derived from HTML 5  
Storage). It would be good to explore further collaboration as the  
implementation of the two spec families may follow a common path.  
We've adopted some patterns used in Shindig where appropriate (however  
its worth noting that implementing the W3C spec is far more  
straightforward than implementing Gadgets and OpenSocial).


We've also been working with the Sakai3 project which have already  
been using Shindig, and have recently been experimenting with Wookie  
for the reason stated above - to transparently offer choice to their  
users of widgets using both W3C and Google spec families.


On the client implementations side: I think we should look at  
splitting out some of the parts of the system into libraries that can  
be reused in client implementations - I know a few people who are  
already interested in doing some Android and iPhone apps - for  
example, a framework that wraps a W3C Widget in an iPhone container  
for submission to the App Store. Peter Paul Koch has also been  
lobbying Google to support W3C Widgets in Android natively, and it has  
also been discussed in the Android OSS community as a good idea for a  
potential community project.


On implementation - so far we haven't come across any major issues in  
moving from client to server-side other than same domain/cross-site  
access, which we solve via server-side proxying (exactly the same as  
Shindig - in fact we have a config switch that lets deployments use  
Shindig's proxy rather than ours). However I think looking forward it  
would be good to consider CouchDB and Cassandra for storing Widget  
state data (preferences and shared states) rather than MySQL as key/ 
value persistence is a good fit for widget states, and this may  
perform better under high load situations.


I hope this answers your questions.

Best,

Scott Wilson


* Our team had originally implemented functionality equivalent to the  
Google Wave Gadget API as an extension of W3C Widgets around 18 months  
before the Google announcement, but adopted the Google API for  
pragmatic reasons - we'd rather follow specs than create them.


On 5 Jul 2009, at 22:38, Sylvain Wallez wrote:


Ross Gardler wrote:

I would like to submit the Wookie project proposal to the Incubator
PMC. Our draft is appended to the end of this mail and is available
at:

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

A quick overview of Wookie is:

Wookie is a Java server application that allows you to upload and
deploy widgets for your applications. Wookie is based on the W3C
Widgets specification, but widgets can also be included that use
extended APIs such as Google Wave Gadgets and OpenSocial.

I have agreed to champion and mentor this proposal, Gavin McDonald  
has

also agreed to mentor, more mentors are being sought - let me know if
you are interested.

At this stage I am seeking feedback on or questions about the Wookie
proposal.  The project team are subscribed to this list and ready to
respond to any queries.



The W3C widget spec is more targetted at standalone installation of  
widgets (like the Mac's Dashboard, Yahoo widgets, Vista widgets,  
etc) and Wookie as I understand it aims a providing a server-side  
implementation of this specification. This is an interesting point  
of view that can allow a wider audience to use this specification  
that is currently mostly of interest to mobile phone vendors. Now  
I'm curious to know if a server-side implementation will not hit  
some technical difficulities related to the implementation of a  
client-side specification (I saw that already with XForms).


What's interesting also, is that W3C widgets and OpenSocial gadgets  
are more or less competing specifications, and it seems from this  
proposal and what

48 matches

Mail list logo