Jump to content

Michael Aivaliotis

Administrators
  • Content Count

    6,156
  • Joined

  • Last visited

  • Days Won

    91

Everything posted by Michael Aivaliotis

  1. GPM extracts code into your project, BTW. VIPM, NIPM and GPM provide built products of reusable code, among other things. I believe what you are saying is that you consider existing, cloud-based source code control tools such as GIT as a viable option for reusable code distribution. This shouldn't be limited to packaged stuff.
  2. I agree. I don't store those type of file in the repo for a while now. My specific comment was about how to transition from one large files extension in Mercurial to Git. I use Bitbucket Downloads. However, I'm finding that different file sharing tools can be useful for different use-cases. There's really no one-size fits all.
  3. I sign all my built EXEs, for all my customers. It's trivial to do and doesn't cost much. This also allows me to know if the application that I'm asked to support was built by my company or the customer did the rebuild themselves.
  4. What's the reason for moving to Github? I was using Kiln to host my code, which used Mercurial. I switched to Bitbucket with Git. I had to migrate many projects from Mercurial to Git. I did the migration using the HG-GIT extension: https://hg-git.github.io The main problem I encountered was using the "large files" Mercurial extension. The automatic import tools provided by GitHub and others don't like that extension and barf. Otherwise you can use the web migration tool provided by GitHub. My workaround to the large files problem was to accept the fact that I will lose the revision h
  5. Published 10/29/2019 See here: https://finance.yahoo.com/news/national-instruments-announces-plan-ceo-200200768.html AUSTIN, Texas--(BUSINESS WIRE)-- NI (NATI) today announced that Alex Davern will step down as Chief Executive Officer of NI, effective January 31, 2020. The NI Board of Directors has appointed current President and COO, Eric Starkloff, as NI President and CEO, effective February 1, 2020. Davern will take up a teaching position at the University of Texas McCombs School of Business starting in the Fall of 2020. Davern will remain on staff at NI as strategic advisor
  6. Does this mean the Actor Framework functionality will now be represented graphically in NXG, as apposed to a list of hundreds of class VIs in a tree in the project?
  7. Just watched this presentation by Richard Feldman called: Why Isn't Functional Programming the Norm. As I was watching this, many ideas came to mind about how LabVIEW stacks up in various areas of the presentation. I wanted to hear what the community thinks about this. We can all agree that LabVIEW is NOT a popular language (as defined in the video) and it probably will not end up on any presentation as the one in this video (I desire for this to change though). However, I think the discussion in the community about FP vs OO is currently taking place. I know people that do not u
  8. @Jim Kring, it seems to me that the export of the code has gotten a positive response from the community. However I may be wrong. If anyone has any opinion either way, please come forward. As you can see in this thread, it appears the community has rallied around this effort. This is why I emailed you to come here and share your thoughts. In the past, OpenG was a great venue to showcase how a bunch of passionate LabVIEW users can come together and collaborate on something useful. The passion is clearly still there, as shown by the numerous discussions here. The general coding community ha
  9. I can see why you asked that question. It seemed to come out of left field. The intent is not to fork OpenG or create a separate development branch. The intent is to facilitate community involvement and incorporate some of the ideas floating around here on LAVA into new future builds of OpenG. JKI has taken some of the libraries, not most. I counted 5 on JKI and there are around 23 that I found and migrated. Granted, some of them could possibly be merged into new or cleaned up. However, this can be decided by the community. I think having a location that the OpenG community can call their
  10. I'm glad to hear that you are welcoming to this. I think this initiative and the positive response shows that the community is willing to take on some of these tasks and responsibilities as long as there's an open and inclusive process in place. As a starter, it would be great to revive the openg.org domain which has been dead for many years and at least point it to the LAVA OpenG root forums,. That's where it was pointing to before as indicated by this post. In the future, it could point to a GitHub landing page.
  11. It seems like OpenG needs a landing page. Perhaps if we use GitHub Pages for the GitHub repos, as proposed here. This could be the new URL to include in licensing.
  12. Good points. You can't create a wiki for an organization. I've setup an OpenG team, but even there, no wiki support. Limitations... However, each repo has its own wiki. Which is good for content related to that specific repo. It's possible now with separate repos, to have each one have it's own LV version and build/release process if needed. However, if not, then each wiki can simply have a link to some global page that covers the overarching policies. This could be on LAVA, but I think the LabVIEW Wiki could provide support here. There could be a single page there covering everything, which i
  13. NI does (Stephen Mercer) not recommend using them pre-official release version.
  14. I wanted to do a live video stream to discuss the topic of collaborating on OpenG code on GitHub. I realize that this can be a very long discussion going in many different directions. But for now, I just wanted to keep it simple to the basics of GIT and GitHub. There could be more livestream discussions later about any topic. But just wanted to gauge interest and see what the community thought. I wanted to make this a livestream because it would allow you to ask a realtime questions and it would help focus the info on stuff you are interested in.
  15. Sort of. I think Github uses the email address, not the username. I've asked @Rolf Kalbermatter for his GitHub email, because it didn't work with his username. I decided to leave the repos under GCentral and use the OpenG prefix as suggested.
  16. I've started adding repos: https://github.com/Open-G
  17. @LogMAN, Is it possible to remap a source forge username to a GitHub username?
  18. Can you describe the workflow? This doesn't seem to be a good solution on first blush.
  19. @Rolf Kalbermatter, I will be redoing the export today based on the new scripts, if they work. So if you committed code recently, it will get included. I think you are the only one working on any code at the moment. I will add you as a collaborator on the repo so you don't need to fork. Once the conversion is complete: Make a branch on the git repo. Checkout the branch Do a file diff between your local SVN and the Git branch. Copy over the changed code from SVN to Git. Commit the branch. @LogMAN, unfortunately GitHub does not have a good way to group relat
  20. Thanks @LogMAN. After I get paying work done, I will try this out. For anyone else following along. If you are currently an OpenG developer ( @Rolf Kalbermatter?) and want to be added to the OpenG team on GitHub, send me a PM.
  21. We can create a VIM array package for OpenG that is separate from the other array package. We could call it something else. So it could be distributed in 2017. Currently the entire OpenG sources are in a single repo. So you have to build everything in one LV version (2009). If we made each package its own repo then it could have its own LV versioning roadmap separate from the whole. See discussion here.
×
×
  • Create New...

Important Information

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