Hi Pawel,
the Matterhorn project is currently in a shift from a founded project to
a community based project. One of the manifestations of this change is
the upcoming Matterhorn Board election.
The board will make the more strategic decisions. The operative
decisions will be made by the committers.
You can make proposals on the Matterhorn mailing list
([email protected]). And the people on the list can vote on
you proposal. If the proposal got only positive feedback with in at
least 3 weekdays it is accepted.
The software development strategy (at least in the founded project) was
a kind of agile. So the philosophy was: implement something, and rewrite
it, if it the implementation is insufficient, for future needs.
Because of this you can not expect the APIs to be stable for new
releases. Some of them are quick-and-dirty approaches and need to be
re-factored sooner or later. That's why we currently settled on the
concept that Greg explained already.
Maybe it is necessary to change the software development strategy. Feel
free to advocate a new approach on the mailing list and in the weekly
video-conference meetings on tuesday (8 a.m. PST).
Rüdiger
Am 13.09.2011 15:03, schrieb Pawel Fic:
I don't mind freezing API. But it receantly changed. If it will
survive three consecutive releases (1.3, 1.4, 1.5) - we can talk about
freezing it. Right now it is too early. We will just spend time
chatting about it.
I think a detailed spec for the API would solve the problem. I think
this would increase the value and quality of the server itself.
However, there are following questions:
- who is the person that can approve this idea / other idea?
- who is the person that can approve the spec ?
- who will develop a spec (a list of people)?
- when the first revision of spec will be finished (like this week /
next week ) to be aproved by appropriate person?
Maybe there are other questions like:
- is the API needed at all ?
- do we want third party Capture Agents/Schedulers/Content Servers to
integrate with Matterhorn?
There are hundrets of questions I want to ask about the API, but this
thread is not a right place. I would love to post them later to
people that will be approving/documenting API (I think I can help
documenting the API) but right now - Important question (for this
thread / and or Matterhorn) is how to solve (Hank's, mine,
Matterhorn's) problem with API that I think is not documented and
instantly changing. Previous post contained some examples.
It is really my business here to agree/understand the API / integrate
with Matterhorn.
Can we agree on how to solve this problem (what to do) in two days ? I
guess since we are from all over the world then lets say in 48 hours.
:-) And then solve it in a week ?
BTW: We need a person or some kind of Matterhorns Board to approve the
solution, right? If there are no people that manage the project we
need to start a revolution, step up and set a direction and
destination. :-)
-Pawel
Well, I would say "how can the API *not* be frozen at this stage
of development?". I mean, Matterhorn is not in a beta version.
It's 1.2. One would expect some well-developed APIs at this stage,
it's not like we have not tested the system and we don't know what
we want it to do and how.
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
--
________________________________________________
Rüdiger Rolf, M.A.
Universität Osnabrück - Zentrum virtUOS
Heger-Tor-Wall 12, 49069 Osnabrück
Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
E-Mail: [email protected]
Internet: www.virtuos.uni-osnabrueck.de
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
