Update of /cvsroot/community/www/2005/telecon/minutes/text
In directory cvs:/tmp/cvs-serv19847/minutes/text

Added Files:
	071205-telecon-notes 
Log Message:
added telecon notes for 0712 telecon and updated index with link to this.

--- NEW FILE: 071205-telecon-notes ---
List Of Attendees
-----------------
1. Luis Saldana (DextraTech)
2. Alberto Meza (DextraTech)
3. Edgar Luevano (DextraTech)
4. Donya Shirzad (RealNetworks)
5. Jeff Wannamaker (RealNetworks)
6. Scott Nelson (RealNetworks)
7. Kevin Scott (Nokia)
8. kevin Foreman (RealNetworks)
9. Mike Frazier (RealNetworks)
10. David Hirayama (RealNetworks)
11. Rishi Mathew (RealNetworks)
12. Milko Boic (RealNetworks)
13. Michael Maloney (RealNetworks)
14. Haydon Boone (RealNetworks)
15. Anand Vaidyanathan (RealNetworks)


*************************
Topic -  Document Submission Guidelines
*************************
[Rishi] I just posted the document yesterday.... I havent heard back from anyone except Milko.  I have made changes based on his suggestions and will be posting that soon
[Donya] did we decide to post this under the devdocs section
[Rishi] yes
[Donya] for The player project, the devdocs is being used for something else & not for specs and we dont want to mix stuff up
[KevinF] Alan said last time that the process looks good but the project managers need to review and complete the process.  Kevin, do you have anything to add?
[KevinScott] I dont have anything to add and Alan is not on the call
[KevinF] What is the resolution between Donya and Milko?
[Donya] I will talk to my folks and let you know
[Anand] so each project would have a devdocs directory?
[Haydon] as against the www directory wehre our tech writer puts tech stuff
[Rishi] the devdocs lives under www/2005/devdocs
[Haydon] both sdk documentation and white papers live there?
[Milko] i agree with rishi
[Haydon] so engineering will put docs in devdocs, Doug would take them and massage them to create his tech docs.  should he keep the docs where they are
[Kevinf] yeah they stay where they are
consensus

*************************
Topic -  Cayenne status updates
*************************
[Milko] strained by QA resources, 23 bugs open now.  heading towards cayenne gold release.  We are working on an appendix to cayenne containing H.264
[Milko] we had talked about H.264 in earlier conferences, but had not committed to development to this
[KevinF] Nokia already had a plan for H.264 development effort -- and wanted to contribute that.  has that status changed?
[KevinS] we have our dev plans on target -- but our devs have been held up with other work
[Milko] we are working on that , but if Nokia is working on that as well ... in order to prevent any duplicity of work i was wondering if we could work with nokia on the community on this
[KevinS] We havent started working on this in the helix community 
[Kevinf] so there is gonna be an announcement in the community ... milko you wanna say something on that
[Milko] we have been working with atul's team, and will make the announcement when we are ready for that, but its really close to being completed
[KevinS] is there any work on the producer side for that
[Milko] Not yet
[KevinF] but there is some work being done in the Sutherland side of the dev effort to incorporrate h.264.
[Milko] the REal product supports this -- the open implementation does not

*************************
Topic -  Next client platform release. 
*************************
[Milko] we are wondering what dev contributions would we get from other community members w.r.t to the next cliuent platform release -- specifically h264 and the kind
[KevinS] from the nokia side, we are willing to help
[Milko] that is great that you are willing to help.  Any idea of what process we need to follow?
[KevinS] i dont know actually.  What is the helix approach for getting contribution and participation for outside parties
[Milko] The process is that the concerned party would be creating a project and working within that and merge the main branches
[Milko] I wanted to find out what help we can get in the near term
[Milko] We have most of the work done , but some parts need work and we are strained for resource to get this shipped on time, but the parts that remain would be of particular interest to folks like you kevin.
[KevinS] i am not in a position to make a comment.  We will have to loop Alan in
[Milko] We have created a plan for including features for the next 6 months features like super buffer support, stream recording, universal playback support, au support, dvd playback, engine extender kit  etc. should go into the next release
[KevinF] We have been talking about this for the last few months.  but Kevin, what would be you top 5 features that you would lilke going into the next release.  That way we can get some feature proposals from multiple sources and get a team together and talk those over eithr dallas or call a cayenne summit in Seattle
[KevinS] we are open to both
[Milko] Cayenne is not getting any more dev work put into it
[KevinS] I was talking about the features for Cayenne2
[Milko] we should be thinking about hte next 6 months for cayenne2 features .. 6 months is a rough time frame, but some fixed release schedule
[KevinF] we should get people together for featureRequests and feature proposals and get a list locked and loaded for the next platform core.
[KevinS] Milko, do you have a date in mind for hte next release.
[Milko] dont have a date yet.  we are ramping down on the current cayenne and working on the next cayenne features now.  In six months time, our status on the next cayenne would be the same as the status that we are at today wrt our current product
[KevinF] so milko, what do you think of putting the requiremtnts to the community
[Milko] will absolutely follow the process as we have been doing
[KevinS] fine from us
[Rishi] we might have to figure out a process similar to the doc submission process to make sure that community feedback is heard and recognized
[KevinF] milko means that we should not lose the momentum and keep going forward with the dev effort we have today
[Kevinf] milko are you saying that cayenne will be stable in Nov instead of sept
[Milko] we will definitely have gold quality code by nov but it could be sooner we are restrained by lack of qa resource
[Michael] it is also dependent on how the qa tool is received
[Milko] the estimates I provided are those i got from the realnetworks qa dept and nto from the community.