Splitting the FlySight repository

29 views
Skip to first unread message

Michael Cooper

unread,
Feb 21, 2014, 10:03:39 PM2/21/14
to flysig...@googlegroups.com

Hi All—

 

It’s been suggested to me that it might make sense to split the FlySight repository into three separate repositories, say:

 

flysight/flysight

flysight/flysight-viewer-mac

flysight/flysight-viewer-win

 

The first would contain firmware, with viewers moved to the other two. There are a couple of reasons for the change:

 

-          No code is shared between the three repositories.

-          The three repositories use different build processes.

-          They are essentially three separate projects.

 

It seems like it would be better to make the change sooner rather than later, but before I go ahead and split the repository, I wanted to touch base with all of you and check that this doesn’t seem like a really bad idea to anyone. :-)

 

Does anyone have any serious reservations about this change?

 

Michael

Solutions Mann

unread,
Feb 22, 2014, 2:03:06 AM2/22/14
to flysig...@googlegroups.com

To me it’s equally good , all in one place or three separate specific places, I suppose that would be a more uncluttered space.

But to be honest, it’s not that complicated to extract, obtain, upload or  download the correct information, from the current  pages.   

 

--
You received this message because you are subscribed to the Google Groups "FlySight Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flysight-dev...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply all
Reply to author
Forward
0 new messages