Synopsis Software companies, such as Microsoft, create documentation for millions of topics concerning its APIs, services, and software platforms. Creating this documentation comes at a considerable cost and effort. Now, developers are flipping this process by creating their own sources of documentation via blog posts and Stack Overflow questions and answers. For Android, not only can more examples be found on Stack Overflow than the official documentation guide, developers may be getting as much as 50% of their documentation from Stack Overflow. How might the crowd find other ways of flipping the processes of software development?
Bio Chris Parnin is an Assistant Professor at North Carolina State University. He received his Ph.D. in Computer Science from the Georgia Institute of Technology. His research spans the study of software engineering from empirical, HCI, and cognitive neuroscience perspectives. Two recent research topics include A) using fMRI and EMG to actually study the brain activity of developers and B) understanding how crowds of developers come together on sites such as Stack Overflow and Github to contribute software knowledge. He has worked in Human Interactions in Programming groups at Microsoft Research, performed field studies with ABB Research, and has over a decade of professional programming experience in the defense industry. Chris's research has been recognized by the SIGSOFT Distinguished Paper Award at ICSE 2009, Best Paper Nominee at CHI 2010, Best Paper Award at ICPC 2012, IBM HVC Most Influential Paper Award 2013, featured in Game Developer's Magazine, Hacker Monthly, and frequently discussed on Hacker News, Reddit, and Slashdot.
After months of hard work and phone tag by TriLUG sysadmins and volunteers, our new server, Moya, has been racked and installed in temporary housing! (Thanks to MetaMetrics for providing the space!) Our mission tonight is to set up basic virtualization infrastructure to run the next generation of TriLUG services, and to stand up a replica of our current server, Pilot, to assist in porting services over.
We will plan and coordinate our efforts in advance on the #trilug-sys IRC channel, on irc.freenode.net.
Tonight's meeting is sponsored by All Things Open, a conference exploring open source, open tech, and the open Web in the enterprise. All Things Open will be held October 19th & 20th in the Raleigh Convention Center.
Synopsis Using free and open source software, and participating in the associated communities, can make you more employable! This presentation will cover how to get started as a community participant and how to gain résumé-enhancing experience. Special guests representing a variety of local organizations will then join us for an interactive discussion about hiring trends, which FOSS skills make a candidate stand out, and any questions you may have for someone directly responsible for hiring FOSS-experienced engineers.
Bio Michael Hrivnak, the presenter and panel facilitator, is a Principal Software Engineer at Red Hat and Team Lead for the Pulp Project. With strong experience in both software and systems engineering, he is excited to be writing software for systems engineers. Michael is passionate about open source software, live music, and reducing energy consumption.
Topic: Workshop on Containers and TriLUG Infrastructure When: Thursday, 20th August 2015, 7pm - 9pm Where: Bandwidth, Venture III, 900 Main Campus Dr, Raleigh, NC 27606; and #trilug-sys on freenode Parking: Venture Center Deck, adjacent to Venture III on Venture Center Way (visitor spaces are unrestricted after 5pm) Map: Google Maps
Work on a personal project, hone your skills, or try something you learned about at a recent meeting. While you're at it, help us maintain the TriLUG infrastructure.
This month we'll be mostly playing with personal projects while we look forward to our new server coming online. Come on down and hack on something fun, or play around with Docker, maybe containerize a favorite application.
Synopsis Duke University provides access to a wide variety of Linux applications, for student projects, teaching, and research. Besides provisioning hundreds of traditional Linux VM's each semester, Duke is taking advantage of emerging container technologies to host applications.
This presentation will explore a few of the technologies and tools Duke has used for application delivery, including the 350 Ubuntu containers running on Docker that host R and RStudio for statistics courses, and the noVNC/OpenBox solution used to embed X Windows applications in users' Web browsers. (Source code for some of this technology will be available on GitHub.) It will also discuss more generally the strategy and the tradeoffs involved in providing virtualized applications - especially when you have to give sudo access to students.
Bio Mark McCahill works at Duke University's Office of Information Technology, as an architect for e-learning and collaborative systems. He was involved in the development and popularization of early Internet technologies - most notably at the University of Minnesota, where he led the team that developed Gopher. He is also interested in virtual worlds, developing the GopherVR system for organizing Gopher information spatially, and serving as an architect of the Croquet project.
TriLUG welcomes speakers on any topic related to free and open source software! If you have been invited to speak at TriLUG, or you would like to propose a talk yourself, read this page for information about what to expect.
If you are interested in speaking, please email firstname.lastname@example.org with the topic you would like to speak on, the dates on which you are available, and a brief biography. You can also contact us if you have any questions about speaking which are not answered on this page.
Format: TriLUG talks are delivered in a lecture hall or similar space, to an audience of anywhere between 40 and 100+. The "talk" section of each meeting lasts 70-90 minutes, including questions (however you wish to handle them).
Subject Matter: Anything related to Free and Open Source Software is fair game. This includes presentations about and demonstrations of particular software, but it also includes talks about the community aspects of FOSS, such as career development, community management, technical writing, presentation skills, and applications of FOSS in society.
We prefer talks that appeal to a broad range of FOSS users, including software developers, system administrators, community leaders, and hobbyists, using a variety of technology stacks, and at varying experience levels. As a 501(c)(3) non-profit organization, we cannot engage in political campaigning, and prefer to avoid explicitly political topics.
Anti-Harassment: As stated in our anti-harassment policy, TriLUG is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity, sexual orientation, disability, physical appearance, body size, race, religion, country of origin, or age. We expect speakers to abide by this policy, and therefore to refrain from offensive verbal comments, deliberate intimidation, and sexualized images, activities, or other material.
(If you feel that you are particularly likely to be targeted for harassment, we can make special arrangements to ensure your safety.)
Date and Time: TriLUG meetings are held the second Thursday of each month from 6:45-9pm. We are always looking for speakers.
Location: We are currently hosted at the NCSU College of Textiles, meeting in room 1120. The room is marked with a circled star near the top left of the map (the parking entrance is marked with a circled "P" around the bottom center).
Audio, Video, Power: We will ensure that a projection screen with an HDMI, Mini-DisplayPort, and VGA laptop connector is available for presenters to use at each meeting, as well as at least one power outlet. If you need additional audio, video, or power capabilities, let us know in advance so that we can contact our hosts. If you plan to use a laptop to project slides or other material, we would appreciate if you allowed us to use it to project the meeting introduction slides.
Recording: Generally, TriLUG meetings are recorded and posted on YouTube. We can make exceptions if you would prefer not to be recorded.
Food and Beverage: Pizza and soft drinks are provided for attendees at each meeting. We do not currently make accommodations for vegans or gluten-free persons, but we may be able to do so upon request. Alcohol is not permitted at meetings.
Post-Meeting: After each meeting, we hold "TriCHUG" at a local restaurant (Ba-Da Wings in the Mission Valley Shopping Center) for food and/or beer. Usually about 10-12 members attend, but it is completely optional for speakers. (And despite the name, nobody gets hammered.)
Expenses: We currently do not have the funds to cover speakers' travel expenses or other expenses. (Someone may pay for your meal at the post-meeting, though.)
Synopsis Free and open source software owes its existence to copyright laws, but as the community has grown, understanding of copyright and licensing has diminished. Source code hosting sites are now replete with improperly licensed projects, license violations, and users and developers who are unclear what rights they actually have. But it doesn't have to be this way!
This presentation will open with a crash course on copyright, and then narrow its focus to issues related to Free Software licensing -- how the licenses actually work, how to choose a license appropriate for your project, where trademarks and patents fit into all this, and what licensing things you should NEVER EVER DO. We'll close with a look at the Supreme Court's recent decision in Oracle v. Google and its implications for free software.
Bio Matthew Frazier is TriLUG's PR Officer and a recent graduate of NC State University's Computer Science program. At NC State, he developed and taught the Digital Millennium Copyright Class, a one-hour seminar course on modern copyright issues. He enjoys participating in the free/open source software community by presenting and teaching at conferences and user groups. (And sometimes he even writes code.)