Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Discussion: Mars simultaneous release participation

Your plans are great. I would like to work on the tooling.

I would also like to see work done where the endpoint of a remote service is not a remote service. For example, we now have some RPi work but this requires Java and a remote service to run on the Pi. This will not be feasible in the IoT world because you cannot just run Java on a resources depleted microcontroller.

However, it would be nice if we could run a remote service on the manager and something very thin on the microcontroller (e.g. radio, Infrared, Bleutooth with a tiny comm layer)

Cheers,

Wim


On Wed, Nov 12, 2014 at 3:11 AM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
On 11/11/2014 12:01 PM, Wim Jongman wrote:
I can help but I require a plan and management (i.e. someone who tells me what to do).

Oh don't worry, there will always be someone to tell you what to do :-)  :-)

For the beginnings of a technical plan for Mars, see [1].   Since ECF is a community-driven project, if people want other/additional to what I've articulated in [1] then they should feel very welcome to participate in the planning by speaking up about what they want to see, and then doing what they can to make it happen.   Contributors will define the plan whether ECF participates in Mars or not.

As an independent-led community-driven project, ECF doesn't have a corporate project management.  I consider that a strength for the project, as it allows us to do things that would be difficult or impossible in many corporate environments, like create open transport-independent communications and messaging infrastructure (e.g. OSGi Remote Services/RSA).   It's very liberating (IMHO) to be able to create communications infrastructure that does not attempt...or even allow...lock-in.   However, it also means committers and contributors need to be self-motivated, and contribute in the absence of some structure.  Sadly, these days it also means operating without some of the resources that are traditionally provided by management.

So thank you for the offer of help Wim, but I would like to request that everyone try to be a little more specific about what they can/will do to help satisfy the Mars Simultaneous Release requirements.    Perhaps an hours-per-month estimate...just as an example of one way to be specific.  If you can think of other ways to be specific then feel free to use them.

Thanks,

Scott

[1] http://dev.eclipse.org/mhonarc/lists/ecf-dev/msg07122.html




Cheers,

Wim

On Tue, Nov 11, 2014 at 4:57 PM, <slewis@xxxxxxxxxxxxx> wrote:
Hi Folks,

Do people have comments on ECF's participation in Mars Simultaneous
Release?  I have to decide by M4+0, which is December 12.

At this moment, I am not inclined to commit to ECF's participation in
Mars, as it requires a fair amount of additional work (e.g. published
plan, releng, IP, meeting SR requirements [1]) of questionable benefit to
ECF consumers (see below).

This year, I'm not able to commit to doing all this work by myself, and so
will need additional commitments from the ECF committers and community in
order for us to participate in the Mars SR.

Scott

[1] https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements




> Hi Folks,
>
> Since it's beginning nine years ago, ECF has participated in the annual
> Eclipse Foundation simultaneous release.    Over time, participation has
> added much value for ECF consumers, as the requirements for
> participation [1] have resulted in ECF having very reliable/predictable
> releases and higher quality via all of the associated release
> engineering (e.g. a stable and flexible build, automated testing,
> supporting multiple distribution targets, documentation, etc).
>
> Another potential benefit of the SR is the associated
> marketing/visibility for the project.   I would argue, however, that ECF
> gets very little marketing value from the EF, and that seems to me very
> unlikely to change.
>
> There are significant repeating costs on ECF:  i.e. meeting all of the
> requirements [1], preparing and doing reviews, submitting plans, etc.,
> etc.   At this point, meeting many of these requirements have been
> nicely automated via our previous release engineering work (primarily by
> Markus K and others), but unfortunately many of them can't be automated,
> and the resources to complete these requirements (e.g. my and others'
> time) are becoming more restricted.
>
> Questions to discuss:
>
> 1) Do people see continued value to ECF committers/contributors and
> consumers in participation in the SR?
> 2) If your answer is yes:  are you willing to provide resources (i.e.
> committer and/or contributor time) to make this happen?
>
> The time driver for this discussion is that all participating projects
> must declare their intention to participate by Mars M4, which this year
> is December 12.   I'm starting this discussion early so that everyone in
> the community that wishes may provide input to the decision.
>
> Thanks,
>
> Scott
>
> [1] https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements
> [2]
> https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev



_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev


Back to the top