Thomas Beale
Jun 16, 2012, 11:47:43 AM6/16/12
to eiff...@googlegroups.com
All,
I have created some initial 'about' content for the community. Yes, I know, this is presumptuous, but I am hoping that this community will be broadly interested in these ideas and/or morph them into more representative ones. See http://www.eiffelhub.org/node/1 .
According to the ideas posted above, I think there are various practical activities that can occur in parallel:
* the 'identify' stage - setting up some kind of register of existing components. I know this has been done 10 times before, and a starting point is probably one of the previous lists.
* the 'describe' activity - some components have active maintainers and can be 'described' - for this we need to decide on a set of adequate meta-data
* the 'accession' activity - actually moving code into the EiffelHub.github area, and putting it under some sort of known management
* the 'roadmap' activity - defining target structure & contents for a coherent application and system development environment.
For some time initially, it would be good just to do the first 2 items, I suspect. Question: how do we want to go about setting up a register of existing code? It could be a page on the website, but ideally we want to be able to query it. I am a Drupal newcomer, so am unclear on what is behind Drupal, in terms of helping us build queryable website content.
This question also applies to the 'describe' activity, since ideally we want to be able to query the component descriptions.
thoughts?
- thomas beale
I have created some initial 'about' content for the community. Yes, I know, this is presumptuous, but I am hoping that this community will be broadly interested in these ideas and/or morph them into more representative ones. See http://www.eiffelhub.org/node/1 .
According to the ideas posted above, I think there are various practical activities that can occur in parallel:
* the 'identify' stage - setting up some kind of register of existing components. I know this has been done 10 times before, and a starting point is probably one of the previous lists.
* the 'describe' activity - some components have active maintainers and can be 'described' - for this we need to decide on a set of adequate meta-data
* the 'accession' activity - actually moving code into the EiffelHub.github area, and putting it under some sort of known management
* the 'roadmap' activity - defining target structure & contents for a coherent application and system development environment.
For some time initially, it would be good just to do the first 2 items, I suspect. Question: how do we want to go about setting up a register of existing code? It could be a page on the website, but ideally we want to be able to query it. I am a Drupal newcomer, so am unclear on what is behind Drupal, in terms of helping us build queryable website content.
This question also applies to the 'describe' activity, since ideally we want to be able to query the component descriptions.
thoughts?
- thomas beale
Thomas Beale
Jun 16, 2012, 12:37:01 PM6/16/12
to eiff...@googlegroups.com
On 16/06/2012 16:47, Thomas Beale wrote:
All,
I have created some initial 'about' content for the community. Yes, I know, this is presumptuous, but I am hoping that this community will be broadly interested in these ideas and/or morph them into more representative ones. See http://www.eiffelhub.org/node/1 .
According to the ideas posted above, I think there are various practical activities that can occur in parallel:
* the 'identify' stage - setting up some kind of register of existing components. I know this has been done 10 times before, and a starting point is probably one of the previous lists.
* the 'describe' activity - some components have active maintainers and can be 'described' - for this we need to decide on a set of adequate meta-data
* the 'accession' activity - actually moving code into the EiffelHub.github area, and putting it under some sort of known management
* the 'roadmap' activity - defining target structure & contents for a coherent application and system development environment.
For some time initially, it would be good just to do the first 2 items, I suspect. Question: how do we want to go about setting up a register of existing code? It could be a page on the website, but ideally we want to be able to query it. I am a Drupal newcomer, so am unclear on what is behind Drupal, in terms of helping us build queryable website content.
This question also applies to the 'describe' activity, since ideally we want to be able to query the component descriptions.
thoughts?
- thomas beale
--
You received this message because you are subscribed to the Google Groups "Eiffel Hub" group.
To view this discussion on the web visit https://groups.google.com/d/msg/eiffelhub/-/IqT62aJw3YQJ.
To post to this group, send email to eiff...@googlegroups.com.
To unsubscribe from this group, send email to eiffelhub+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/eiffelhub?hl=en.
--
|
Thomas Beale Chief Technology Officer, Ocean Informatics Chair Architectural Review Board, openEHR Foundation Honorary Research Fellow, University College London Chartered IT Professional Fellow, BCS, British Computer Society Health IT blog |
Thomas Beale
Jun 25, 2012, 4:16:55 AM6/25/12
to eiff...@googlegroups.com
Any reactions?
On 16/06/2012 16:47, Thomas Beale wrote:
Jocelyn Fiat
Jun 25, 2012, 4:34:08 AM6/25/12
to eiff...@googlegroups.com
About drupal, we can create new content type, and within drupal, we
can precise the different fields.
Once we have that, I guess we need to build a specific drupal module
to be able to search/query ... those specific content types.
Now, we should know what kind of data/field we want
Once we know that, we can customize drupal to edit/display them.
In the meantime, I guess we can start using Drupal's book, and put the
information in text.
-- Jocelyn
--
Jocelyn
------------------------------------------------------------------------
Eiffel Software
805-685-1006
http://www.eiffel.com
Customer support: http://support.eiffel.com
User group: http://groups.eiffel.com/join
------------------------------------------------------------------------
can precise the different fields.
Once we have that, I guess we need to build a specific drupal module
to be able to search/query ... those specific content types.
Now, we should know what kind of data/field we want
Once we know that, we can customize drupal to edit/display them.
In the meantime, I guess we can start using Drupal's book, and put the
information in text.
-- Jocelyn
> --
> You received this message because you are subscribed to the Google Groups
> "Eiffel Hub" group.
> You received this message because you are subscribed to the Google Groups
> "Eiffel Hub" group.
> To post to this group, send email to eiff...@googlegroups.com.
> To unsubscribe from this group, send email to
> eiffelhub+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> To unsubscribe from this group, send email to
> eiffelhub+...@googlegroups.com.
--
Jocelyn
------------------------------------------------------------------------
Eiffel Software
805-685-1006
http://www.eiffel.com
Customer support: http://support.eiffel.com
User group: http://groups.eiffel.com/join
------------------------------------------------------------------------
Thomas Beale
Jun 25, 2012, 6:26:01 PM6/25/12
to eiff...@googlegroups.com
On 25/06/2012 09:34, Jocelyn Fiat wrote:
About drupal, we can create new content type, and within drupal, we can precise the different fields. Once we have that, I guess we need to build a specific drupal module to be able to search/query ... those specific content types. Now, we should know what kind of data/field we want Once we know that, we can customize drupal to edit/display them.
ok - if that functionality exists, I'm happy to make a first draft
of the fields - I'll have it done sometime this week. Can we create
a drupal form to capture a 'record' (or whatever Drupal's idea of a
data object or data set is)?
In the meantime, I guess we can start using Drupal's book, and put the information in text.
there is other stuff I think we can document in this way. I'll do
some work on that this week.
- thomas
- thomas
Alexander Kogtenkov
Nov 9, 2012, 2:51:03 AM11/9/12
to eiff...@googlegroups.com
If Eiffel Hub is going to take over NICE, it seems to be the good time
to deal with that right now - see today's post to the NICE discussion
group:
Thomas Beale
Nov 9, 2012, 3:35:47 AM11/9/12
to eiff...@googlegroups.com
--
You received this message because you are subscribed to the Google Groups "Eiffel Hub" group.
To post to this group, send email to eiff...@googlegroups.com.
To unsubscribe from this group, send email to eiffelhub+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/eiffelhub/-/tMxDwgt7DcEJ.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Alex,
I agree. So far I have not managed to get anyone to reply to my previous posts on this list about moving forward! Anyone interested in moving on this?
I'll post a reply on that other list.
- thomas
I agree. So far I have not managed to get anyone to reply to my previous posts on this list about moving forward! Anyone interested in moving on this?
I'll post a reply on that other list.
- thomas
Jocelyn Fiat
Nov 9, 2012, 4:42:24 AM11/9/12
to eiff...@googlegroups.com
Hi all,
I am interested as before.
If needed, I am candidate to be on the next board of NICE or EiffelHub, if any.
And I wish to continue the EiffelHub project, maybe more focus on providing resources such as tutorial, but also application framework.
-- Jocelyn
I am interested as before.
If needed, I am candidate to be on the next board of NICE or EiffelHub, if any.
And I wish to continue the EiffelHub project, maybe more focus on providing resources such as tutorial, but also application framework.
-- Jocelyn
Reply all
Reply to author
Forward
0 new messages