Jump to content

Chris Cilino

Members
  • Posts

    27
  • Joined

  • Last visited

  • Days Won

    3

Chris Cilino last won the day on September 29 2019

Chris Cilino had the most liked content!

2 Followers

Profile Information

  • Gender
    Male
  • Location
    Austin Texas
  • Interests
    Creating immediate value using long term perspective
    Applying art and craftsmanship to software development using LabVIEW.
    Removing barriers to collaboration among LabVIEW community members.
    Building tools to help LabVIEW programmers do their work more efficiently (bit.ly/ChrisCilino_CSuite)

LabVIEW Information

  • Version
    LabVIEW 2019
  • Since
    2004

Recent Profile Visitors

3,391 profile views

Chris Cilino's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

19

Reputation

  1. @Manzolli and @Deon Sorry for taking so long to get back to you. The beta website is at https://test.gcentral.org/ Let's use this thread to capture feedback.
  2. Howdy ya'll Thanks for your input. Please keep it coming! I'm trying to minimize my interactions with this thread so as not to inadvertently skew the conversation. I love the technical aspect of this conversation. Sounds like so far in this conversation we're exploring the "How can we do this?". I'd like to propose the additional following set of questions to summarize the virtual coffee conversations we've been having and hopefully merge the conversations (mentioned by Stagg54) in the first post To summarize, here is the logic \ questions that have arisen: The primary question: "How do I (as a consumer of code) prevent unwanted effects from code I download?" Leads to responsibility: Who is responsible to prevent unwanted effects of code? How do the responsible parties prevent unwanted effects of code? There seem to be two ways to prevent unwanted effects: Prevention: don't distribute bad code Mitigation: As a user, I have bad code. I need to remove it. Mitigation spawns two more questions: How to notify people so they can remove bad code? Should people be forced into a system so they can be notified? I'm not suggesting answers to those questions, but want to also throw them into our calculus. Please feel free to comment on those questions and keep the conversation rolling.
  3. Hey Ya'll Just wanted to let you know we're tracking user stories at https://github.com/gcentral/Website/issues. Please feel free to submit issues there and continue the discussion on the user stories here.
  4. Hi @gregoryj Sorry for taking forever to respond. I need to adjust my notification settings apparently. I do use the case that comes with Canakit. I'm able to keep the raspberry pi in the case and even put the lid on because of the ribbon that attaches to the breakout board. I got the ribbon and breakout board from Freenova. My full hardware setup is documented in the bitbucket readme at https://bit.ly/ChrisCilino_LabVIEWCommunityAndRP. And yes... it is fun! Enjoy!
  5. @Bryan Which link are you referring to? I just checked all of them and they seem to be working for me.
  6. GCentral is taking a yearly survey to help identify trends so we have data to back decisions. We're asking for 3 minutes of your time to complete the survey at: https://bit.ly/GCentral_Survey_2020-21 At the end of the survey you'll be able to see a summary of the results. In order to help keep the results accurate, you're allowed to take the survey only once, and requires you to sign in to your google account. Thank you for your time and your opinions. GCentral's success is only measured by its usefulness to you. Help make GCentral what you need it to be. See additional information in the GCentral FAQ. And remember: GCentral is opening VIWeek this Sunday at 9 am CTD (https://bit.ly/VIWeek_GCentralPresentation)
  7. Love this idea! So basically an "idea exchange". I have an idea! Does the solution exist already? Is anyone planning to create it? Can I plan it in such a way that other's can implement it? Can I start implementation so that other's can join in? As a community member I would like answers to all of the above quickly. Is that a fair summary @ChrisStrykesAgain?
  8. #VIWeek The first Virtual LabVIEW Event Hosted By the Community. Starting Sunday, May 17th at 9 AM CDT See the full agenda at https://bit.ly/viweek Cilino VIWeek Intro.mp4
  9. LabVIEW Community Edition rocks! In order to help kick off this momentous occasion, I've put together an example alarm clock. It is broken down into 6 lessons (so far) taking you from blinking an led through creating an alarm clock with a state machine. To download or learn about LabVIEW Community Edition check out GCentral.org Check out the alarm clock here! <-(http://bit.ly/ChrisCilino_LabVIEWCommunityAndRP)
  10. Howdy Brian So this is awesome! I know Jeremy presented some stuff just like this in his NIWeeek 2018 presentation (posted on the LV Wiki). Do you know if something like this was ever exported into a package? I'm having a hard time finding it if it exists.... ironically.
  11. There has been a lot of discussion, which is great, but I feel the need to reiterate GCentral's vision and mission. GCentral envisions a LabVIEW community making the best version of itself by improving its capability through collaboration. GCentral is a non profit organization: for programmers who need to find, share or collaborate on G reusable code or software engineering tools. that provides a platform for G code packages and collaboration resources. that is independent and driven by community experts. GCentral's Mission Enable LabVIEW programmers to collaborate by removing barriers to finding / using code designed for reuse (packaged code) removing barriers to contributing code designed for reuse (packaged code) removing barriers to co-developing code using code with confidence GCentral is package technology agnostic / SCC agnostic GCentral does not endorse or encourage the use of one package manager over the other, nor will we. Each community member can package their code according to their preference. GCentral does not endorse or encourage the use of one Source Code Control Provider (local or cloud based) over the other nor will we. Each community member can use the SCC they prefer. GCentral will ease the pain we all feel when attempting to find and use packages by index the currently available public repositories (Tools Network, GPM, JKI Tools, NI Packages) by indexing an new, un-gated, cloud based storage location that can house any package type. by displaying the index results in a web page / APIs, etc (see https://www.gcentral.org/ for the prototpye) GCentral will ease the pain we all feel when attempting to contribute packages by creating new, un-gated, cloud based storage location that can house any package type (not source). MAYBE creating software to transport built packages from build machine to the new cloud storage location GCentral will ease pain we feel when attempting to co-develop code by Creating template projects for each of the major online SCC. (GitHub, etc). Coming pre-configured to build the package type of your choice and upload to the GCentral package server. GCentral will inspire confidence by Making any submitted package always available. Once submitted, a package cannot be deleted apart from a GCentral administrator. As a result, you can depend on a package without fear of it ever missing. Product pages per package designed to educate on the package and author. The above is a summary of the CLA summit presentation I gave (https://sites.google.com/gcentral.org/website/about-gcentral) The advent of the GitHub Package Registry is very interesting. I've reached out to GitHub to provide clarity on how extensible their framework is. At time 29:44 in the presentation Michael linked above the presenter says "We have a great extension framework for adding support for new registries, which will be opening up in the future". That MAY mean we can provide plugins for their registry to recognize NIPKGs, VIPs, GPKGs. And that may completely solve the "find/use" pain point i mention above... so long as the community is ok putting their packages in GitHub AND sacrificing confidence that the package will always be available to use or link against. In conclusion, GCentral's aim is to impose the least amount of infrastructure on a community member while enabling us to find/use, contribute, co-develop packages designed for reuse. GCentral will use already existing technologies to accomplish its goal and create new technologies where needed.
  12. All In case you haven't already, GCentral could really use your help in getting CLA feedback. If you attended the CLA, summit would you mind taking 10 min to fill out the survey . If you didn't get the chance to attend the CLA summit please feel free to watch the presentation. I've included the presentation outline so you can go to the parts of the presentation you find most interesting. Then we would love your feedback via the survey. We're up to 33 respondents and I'm closing the survey end of next week (Nov 1). We really want to make sure we gather feedback from the community so we know we're on the right track. GCentral is for us as a community. Help us make this happen. Thanks.
  13. As a member of the LabVIEW community I would like to have only one profile so I can have a consolidated summary of my activity in the community (number of ni.com posts, number of packages I've created, average rating on the software I release, etc)
  14. Hi Rolf That's good feedback. The current UI \ UX is just a proof of concept. Once we start designing the actual UI \ UX we hope it'll be efficient to use and pleasant to look at. One other note: the indexer is open source. Please feel free to suggest adjustments by joining the dev team on GCentral's git repo. Keep in mind GCentral.org is in its infancy so we're choosing to sacrifice aesthetics for functionality to avoid bikeshedding. Glad to hear you think GCentral is a good initiative and thanks for your thoughts!
  15. As a participant in the G package community I would like a periodic manifest of all new packages so I can stay up to date on what's new. I want to be able to specify how often I get the manifest and the maximum number of packages listed in the manifest.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.