You look at this empty discussion board and you wonder, is anyone actually reading this thing? Yes, I am reading this thing. Post a question and I will answer, just like on the WCF RIA Services board over at MSDN.
If would be great if you could add a short introduction for people willing to contribute to open ria services in post
* Where and how to report bugs / feature requests (codeplex and/or in this forum)
* Where to discuss new features and their implementation (I guess this forum?)
* What is the idea behind the groups (to discuss implementation if features?)
* Is there a checklist for contributions (such as first discussing in forum then adding issue and after that submit pull request)
1) Bugs and feature requests will be tracked at Codeplex.
2) Yes, discussion should happen here.
3) Not sure about the groups. They are a feature of MonoX so I kind of threw in some random group ideas to see if anything happens.
I am not ready yet to lay down any rules for how contributions will happen. I need to work with Outercurve on that.
Any news on how to contrib yet?
The codeplex has site several issues on it that are marked up for grabs so feel free to have a look and discuss here what you want to take a look at. I haven't put up a full "how to contribute for beginners" page yet because I am a beginner myself. If you follow the guidelines on NuGet's how to contribute page (http://docs.nuget.org/docs/contribute/contributing-to-nuget) that should cover the basics.
Like Nuget, Open RIA Services is an Outercurve project so the CLA agreement is the same process. If you want to contribute more than a few lines of code contact then contact Outercurve at contributions@outercurve,org to sign the agreement. Let me know if the NuGet document works for you, if it does then I will just rewrite it a bit and add it to the project section of the site.
Hi Colin, I've gone through the documents, and the seem simple enough, The only things missing are how you actually assign a task to yourself, and how to join the project as a Developer. I'd like to take a look at the Clientside Properties bug - (Clienrside only Properties being set to null when entity refreshed). This seems a simple issue to fix as and an ideal introduction to the process and the code base.
I thought I had already replied to this but since I don't see it I will do so again.
When people sign the CLA agreement with Outercurve I am notified and I will then add them as developers to the project. That is how I will keep track on who has signed the CLA.
The clientside properties bug is surprisingly difficult to solve. I have some ideas of my own but I am very interested to see what everyone else comes up with.
I've contacted Outercurve for a CLA and I have set myself up a fork, I had trouble with one of the nuget packages (RIAServices.Server.4.2.0), that prevented one of the projected from loading (RiaServicesContrib.DomainServices.EntityFramework) when I did a load packages for solution it did not load it.
I've managed to get a build built but I seem to have problems running the tests. When I run the Silverlight tests the test app just opens up with a restricted height so I can only just see the banners at the top of the page.
I'll also leave some comments about the client side property, with the issue.
Make sure you have the latest release of NuGet installed. I haven't seen issues with the solution as long as that is the case. The Silverlight tests are pretty old, if you set Internet Explorer to compatibility mode then the page should render correctly. However, my focus is on getting Visual Studio to run the tests without having to use the old web client. I am much closer then I was, but there is an issue with the resource files not being setup correctly and getting the various test database sources working has been a bit of a challenge.
Correction to what I said earlier about adding people as developers on the project. When I get the CLA notification I will add you as an editor on the project, not "developer". I had the security roles mixed up, developer actually grants committer status and I am not giving anyone else committer status currently. I want changes to come in as pull requests so that I can get experience reviewing them before they get committed. I may eventually start giving people committer ("developer") status but not yet. Editor status doesn't actually give you anything other than edit rights on the Codeplex wiki, but at least it helps me track you. I wish there was an intermediate "permissions to edit work items but not commit" level.