Jump to content

Michael Aivaliotis

Administrators
  • Content Count

    6,078
  • Joined

  • Last visited

  • Days Won

    80

Michael Aivaliotis last won the day on November 6

Michael Aivaliotis had the most liked content!

Community Reputation

319

About Michael Aivaliotis

  • Rank
    MindFreak
  • Birthday 04/02/1968

Profile Information

  • Gender
    Male

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since
    1995

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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 history on those files. Not a huge deal, since most large files I had were installers and binaries that didn't have revisions per say. So after the migration I did a diff on the project folder, identified the large files, which were missing from the new Git project and just copied them over and pushed them up to the Git repo. Don't forget that the core GIT functionality is the same regardless of service provider. So let's say you found a way to import your repo to GitHub, you can easily turn-around and move it to GitLab, bitbucket or whatever. You're not locked-in. But it might be an issue if you are using an extension that only one service provider supports. The future is GIT. I made the jump over a year ago and haven't looked back. The service provider you choose should give you the tools you need to do your job. The reason I picked Bitbucket was because I liked and used all the other products that Atlassian provides, JIRA, Confluence etc. The tools from Github are a bit weak for my business. I also like companies that continuously improve and invest in their products, among other things. Github seems to be the popular choice for open-source, since that's how it got started. Now that Microsoft owns them, perhaps they don't have to worry about generating revenue (don't know if it's good or bad). But I don't see features that compare to what Atlassian offers.
  4. 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 to the CEO through May and will continue to serve on the NI Board of Directors. Board Chairman Michael McGrath said, “The board appointed Alex as CEO in 2016 to lead the transition from our founder, Dr. James Truchard. Over the past three years, he led NI and shaped a new core strategic vision, expanded our strategy to provide more complete systems for our customers, aligned the company to focus on growth industries and delivered record results. The board’s intention, after a successful transition from the founder, was to appoint the next CEO to lead the company to achieve this new vision. After considering alternatives, we unanimously selected Eric as our next CEO to lead NI into a very promising future. Alex will leave NI stronger, with experienced leaders and a clear strategy. We are excited to have Eric as our new leader as he has proven to the board that he is the most qualified person to take NI to the next level.” Davern, CEO said, “I have thoroughly enjoyed being part of NI’s incredible success since joining in 1994, one year before the IPO, and I am confident the company is well positioned to deliver on its growth strategy. I am proud of the progress our employees made in significantly improving our operating results and we have developed a team of highly experienced leaders. I have worked with Eric for many years and have great confidence that as CEO, he will continue to take NI forward to realize the company’s long-term potential.” Starkloff, President and COO said, “It has been an honor to work alongside Alex for the past 22 years and I want to thank him for his mentorship and his significant contributions to NI. I am confident in our strategy and our team, and I believe we are in a position of strength to deliver on our goals. I look forward to taking on the responsibility of CEO, as we connect our deep engineering experience and software-connected systems with our incredible customers who are taking on the complex challenges shaping humanity.” This leadership transition will be discussed during the Q3 2019 earnings call today at 4:00 p.m. CDT.
  5. 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?
  6. 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 use OO in LabVIEW and many that swear by it. So I think this is a fitting discussion. However, the core question of the presentation as put by Richard is "Does OO features make a language popular?" His argument is NO. I don't think OO by itself will make LabVIEW popular, but where does LabVIEW end up on the reasons for popularity as presented? Or better yet, what can make LabVIEW more popular? Is that something that anyone should care about?
  7. @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 has moved to Git with GiHub being the hub. This seems like the logical next step. Who knows what this initiative will lead to. However, I’m expecting that placing OpenG in a neutral GitHub repo will provide the spark and the tools to facilitate open collaboration, then the community can drive the future. The community is full of smart people who have a desire for clean tested code. And if issues come up, LAVA discussions (or GitHub issues) are there to hash things out. When LAVA offered to host all OpenG discussions back in 2011. it was clear that the community wanted to help. When @jgcode put his standards together for how code should be discussed at that time, It was an exciting time. Since then, many people have come forward with offers to add new code into OpenG and fix bugs. For example @drjdpowell first offered to include his awesome SQLite toolkit for inclusion into OpenG. He got no response either way. It’s a shame to have a platform and forums to allow people to post and discuss OpenG code and then ignore it. If you have ideas on what the future of OpenG is. I’m hoping it’s to be more transparent and inclusive. Providing the tools, resources and some safety checks along the way, is the best way to facilitate passionate individuals to dive in. Do you think keeping the status quo of the past 10 years makes sense? It seems to me that the community disagrees. What do you think?
  8. 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 own is important. Including documentation on how to contribute and providing an open, inclusive, transparent development and deploy process is part of it. Having them on GCentral was my idea. I didn't get official approval from GCentral. I've since moved (and renamed) the repos from where I had them to a dedicated OpenG organization. This way it would truly be separate. If you want me to add you as a maintainer, let me know. If there are any contributions to OpenG that JKI has made on the JKI branch, we should merge them into the new repos. New location: https://github.com/Open-G
  9. 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.
  10. 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.
  11. 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 is also community editable. Creating issues can be done by anyone. So if you want to do that, go for it. If they are invalid, they can be closed later. We should also search here son LAVA and create issues for stuff reported by people in the past.
  12. NI does (Stephen Mercer) not recommend using them pre-official release version.
  13. 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.
×
×
  • Create New...

Important Information

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