start here
This page should be always considered as the first source of information - regardless of what stage of this project we are in. Here we should place all pieces of data, preferably with links to all other media (Gitter chat, GitHub repository, this project's wiki etc. The most current information (with required date-time-stamp in the header) will be added to the top of this page, making it behave as a stack.
Please check my today's comments
Please check my assessment of the project so far and try to answer all my question I wrote there. That will help me to find out where did you take a detour from the prescribed course and I will be able to point you to some specific documents that you did not read so far.
Please be aware that the complete implementation of
is included in the definition of this project. I would suggest to review these 4 pages (including their "children" and create development tasks) for each of them, as soon you find the time for this. It will give you a better assessment of the amount of work left, which might be of interest to Stephen Jebaraj and myself
As some initial ej-widgets are wrapped up to be exposed as Aurelia components it makes sense to create the strategy for the order of ej-widgets wrapping (adding them to the bridge). I would suggest to create all those that are used in the Syncfusion bridge catalog application as parts of its user interface (areas indicated below)
@bharath - please enumerate all these Syncfusion widgets, create the tasks to add them to the bridge and check with me if you are not sure about the order of their implementation (Hint: the menubar that you are currently using is bootstrap menubar and it is a great candidate to get done first
Restatement of the some most important rules
-
The very first document to check daily is the start here. The reason for this is to maintain all key tasks, questions etc. in a single document that can always be referenced later – a feature that is too difficult to do with emails. While it is fine to continue with emails based status exchanges until we become comfortable with using Github for everything, I would urge everyone to reach that level of comport soon :-)
-
Assimilate the information on project organization and let me know when you are happy with that data. Do not forget to ask for any clarification about that if needed.
-
In particular observe that it is the list of issues and related boards (that are just graphical rendering of that list) a key project management tool and everything should start and end there. Each element of that list is either a request for a discussion or a definition of a task (sometimes it might contain several subtasks)
-
Every task is initially owned by Bharath, who will reassign it as appropriate.
-
Discussion about every task should take place on that tasks’s page in the form of comments
-
Any issue that is not "technical" should be discussed here to keep the clear separation between technical and "other" issues
First task to do is define Syncfusion JavaScript collection installation Please take this with utmost care as a bad solution might haunt us for a long time after.
Please check the wiki page initial synchronization by email to understand the proposed bootstrap sequence of this project which requires initial communications to be done solely by email, until the issues in that email get fully resolved and agreed upon