Revision as of 22:48, 5 April 2011 by Wadechandler (Talk | contribs)

Contents Infrastructure for Supporting the NB Community

We have talked about having an infrastructure much like that of the Eclipse community. We came up with the set of information detailed below which we can start to improve here as it specifically relates to and more specifically The NetBeans Project on

We need to work out any other issues needed for the community within the infrastructure in this page. Perhaps we request something special out of Perhaps for those items we come up with other inventive solutions using what we have available now or other free services provided to open source on the internet. Either way, we need to discuss further.

Infrastructure Requirements (Possibilities/Points for Discussion)

Top-Level Projects or Sub-Projects of the NetBeans Project


Sub-Projects of Top-Level Projects


Source Repositories


Auto Update Centers


Continuous Integration


Automated User Testing Environment

This would be some kind of a small pool of virtual machines with a graphical user interface where screen shots could be taken to show different steps of testing and what is appearing on the screen when specific automated user tests are run which test functionality added to NetBeans.

This is lower on the priority list in my opinion (Wade Chandler), but is something we should consider. How time sharing would work with such a thing is something else to consider. Obviously different groups could run some specialized tests on their own machines, but having a specialized set of tests which help make sure projects integrate and work well within the NB ecosystem would be a good thing. How that would work, how well it works, and if it is even possible considering scale is something else entirely.

I think it comes down to how much of this type thing Oracle can and is willing to support in the community. I think initially having something like this would help the NB project test strategic features of the UI in different platforms, and in general make sure the application UI works as advertised.

Mailing Lists




Incubation (from the infrastructure perspective)


Community Processes

We need some process definition to understand how all this will work. How will projects become sanctioned extensions of the NetBeans community? We need some things which give direction and clearly state how this will come about. There are other things which need to be thought through.

===Community Responsibilities (who manages what) NetBeans Project

I think the main NetBeans project content should be managed by the NB team (Oracle employees). This helps pull this into their processes, and too it allows them to handle branding and other things such as news items etc they feel should be on the front page. I feel it would make this more sanctioned within NB world. The community can provide commentary on the top project and a mailing list and forum could be used to drive that commentary.

Project Creation




Auto Update Centers


Old Information (A guide for things to start on this page): Top Level and Sub-Project Support

This has been copied over from a different page and is here for the sake of having the information readily available while thinking about items which need added to this page. Perhaps could have been avoided and just linked to the other page...


Currently there is no ability for someone to bring logic or create it as a full sub-project within the NetBeans infrastructure and community. This limits the types of contributions which can take place out of the box. By out of the box I mean a top level or sub-project is created within the infrastructure, code is built, possible contributors are solicited, mailing lists, forums, source control, etc are setup and a sub-project, as a contribution to the NetBeans community, begins.

To me, this is where Eclipse is beating NetBeans as a community. Such a system allows for companies and individuals to come into an area within the community and establish a foot print and bind resources to the project. It is more of a stake of ownership. But too, this helps bring other contributions to the areas which those sub-projects depend upon such as the base platform.

It also gives people a place to house and build those things while also branding them within the NetBeans community as a whole. This gives a presence. As more do this, it not only gives them presence, but grows NetBeans, the project, the community, the support, user levels, resources, and gives NetBeans more presence as well.

Imagine this as top level projects with the possibility for sub-projects. Thus, there may be a top level project called PlatformX located at and then there may be Granted Central Lookup is probably to small to be in its own project, it is a stand alone idea, and serves at least as an example. It would probably be even nicer if projects could be accessed as sub-domains such as

Proposed Solutions:

  • Can (Kenai) support such features for a domain name or group of projects already? --Wade Chandler
  • If we do not know, then who do we need to be talking with regard to Kenai/ --Wade Chandler
  • How do Oracle folks feel about this in general? --Wade Chandler
  • Too, just like Apache, we need some concept of incubating. --Wade Chandler
  • Project leads need to be able to manage their own project or sub-domain and sub-projects. --Wade Chandler
+1, I like the idea with a kenai support for projects. --Arittner 06:36, 29 March 2011 (UTC)
+1, I like the idea with --Sreimers 15:39, 29 March 2011 (UTC)
  • Projects need
    • Sub-Domains (see the points on top-level vs sub projects in this section)
    • Ability to create sub-projects
      • How would that work with repositories?
      • Would a sub-project of a project use the same repository or a different one?
    • User and Permission Management Facilities
    • Mailing Lists
    • Forums
      • Integration with mailing lists would be nice
    • Web page management
      • Instead of large caching delays, it would be nice if there was some staging environment content developers could login to and see changes immediately. Then, the things everyone else sees could be accessed through the caches and a time delay for something to go live. Would make working on site pages easier to see them in action immediately.
    • Source Repositories
      • One for project web site
        • That or instead us a pattern such as X folder in your repository is your web site
      • One for actual source code
      • These need to be their own repositories separate from the giant single repository currently holding NetBeans
      • It would be nice if like the Eclipse projects, these would support multiple technologies such as SVN and Mercurial at the same time; perhaps git as well
    • CI environment
    • Ability to get built modules and clusters/suites into the correct AU centers
      • Please see the information on incubation for more info


I currently propose we have a way to designate projects as incubating or not, and this determines how those projects show up in AU centers which people can register in their IDEs. For instance, there could be an, incubator.beta, and incubator.release set of AUs and then, production.beta, and production.release. Naming can be worked out later, but that is the general idea for how to manage what is incubating or not.

Projects, while incubating, will still show up as top level projects, but will be marked as such in the header for a warning for anyone viewing them. This should allow for a smoother transition for projects, and less for mentors and Oracle folks to do when something graduates from incubator to production.

Having some property which designates them as incubating allows for them to be able to be located in different search results or link sets. This means if one goes to some link, "Incubating Projects", they will possibly see categories and then projects in those categories and be able to click on them and go to their project pages and sub-domains. --Wade Chandler

Continous Integration

At the moment is the server where CI is done for NetBeans IDE. Is it possible to find an "official" way to open this up (apply for being on CI), so that an important contribution can be build against trunk/releases automatically? --Sreimers 15:39, 29 March 2011 (UTC)

Yes, CI would be great. This is something Apache does for its projects, and it is good. It allows for building, testing, etc. Something different in NB land compared to most of Apache land is automated user testing. Are there any resources for shared visual VMs where AUT could be setup for NB sub-projects? If more clarity is needed on what that means, please let me know. --Wade Chandler

Project Leads and Management

I don't know how user management would work for the sub-projects of a top level project. Perhaps if you are a member of the top-level project, you have direct access to all sub-projects. That sounds reasonable to me. Thus, if you have administrator rights to the top-level project, you then have administrative rights to any sub-projects. --Wade Chandler

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo