Presentation of XEclipse, the XWiki Eclipse Integration, at the EclipseDemo Camps in Iasi.
Event page: http://wiki.eclipse.org/Eclipse_DemoCamps_November_2008/Iasi
We introduced Colibri Skin in version 2.0 (2009) and we have supported it for 6 years (version 7.0). How long do we estimate to have support for Flamingo Skin? How are we suppose to innovate / improve the UI with the current skin/templates structure we have?
Raised questions:
* What will the future of XWiki Skins will be?
* Will we be able to support multiple skins per flavor?
* Will we try to make Flamingo Skin customizable? How this will affect the testing of every possible configuration?
XWiki Product and Community, OW2con'15, November 17, ParisOW2
This presentation provides an overview of the XWiki project and its newest features, followed by a description of the governance of the XWiki open source project and the various rules set in place. The relationship between a company (XWiki SAS) and the open source project will also be covered.
Presentation of XEclipse, the XWiki Eclipse Integration, at the EclipseDemo Camps in Iasi.
Event page: http://wiki.eclipse.org/Eclipse_DemoCamps_November_2008/Iasi
We introduced Colibri Skin in version 2.0 (2009) and we have supported it for 6 years (version 7.0). How long do we estimate to have support for Flamingo Skin? How are we suppose to innovate / improve the UI with the current skin/templates structure we have?
Raised questions:
* What will the future of XWiki Skins will be?
* Will we be able to support multiple skins per flavor?
* Will we try to make Flamingo Skin customizable? How this will affect the testing of every possible configuration?
XWiki Product and Community, OW2con'15, November 17, ParisOW2
This presentation provides an overview of the XWiki project and its newest features, followed by a description of the governance of the XWiki open source project and the various rules set in place. The relationship between a company (XWiki SAS) and the open source project will also be covered.
This is an introduction to BiQ, the world's first SEO suite with granular cost control.
It incorporates details on who is BiQ, the story behind it, BiQ's mission statement, core principles and BiQ's key initiatives for the following stages.
For more information on this, head over to https://biq.cloud/
Lessons from Contributing to WebKit and BlinkBruno Abinader
Being one of the most successful open source projects to date, WebKit development process consists of a series of protocols and strict policies in order to obtain committer and reviewer status. Blink follows a similar approach with committers and scoped code owners, in a similar fashion as Linux Kernel does with its subsystem maintainers. Their open source success is due to not only solid support from major technology companies, but also to the high quality and automated testing performed on patches before submission. In this presentation, Bruno explains how the development process of both WebKit and Blink projects are - from submitting well-tested patches with strict policies to check, get review from community, and commit upstream via commit-queue system (including early warning system bots). This is a very practical talk with live demonstrations of patch submissions on both projects.
10 years have passed since the launch of Restlet Framework v1, the first RESTful API framework created, and thanks to our efforts and our open source community, we have gathered a lot of experience along the way. In parallel, the continuous innovation, competition and maturation in the web API space in general and in the Java space as well has created an opportunity to innovate again. The goal is to have a prototype of the v3 of the framework working, based on Netty and Reactive Streams, supporting HTTP/2 and async APIs in a RESTful way.
Presentation I gave at the OSSGTP meeting (http://ossgtp.org) about new stuff in XWiki Enterprise 2.0 and some of the things in store for the future.
See http://massol.myxwiki.org/xwiki/bin/view/Blog/XWikiEnterprise20AndFuture
Presentation Vincent Massol gave at the OSSGTP meeting (http://ossgtp.org) about new stuff in XWiki Enterprise 2.0 and some of the things in store for the future.
Internal training at [[XWiki SAS>>http://xwiki.com]] about the Development Practices used by the XWiki SAS product team in charge of developing the XWiki open source project (among other projects). Most of the practices detailed are those from the XWiki open source project, defined on the [[dev subwiki>>dev:Main.WebHome]]. However the slides also provide a glimpse of other development practices that are used to complement the open source practices, such as Roadmap preparation and Stakeholder meetings.
More details at http://www.xwiki.org/xwiki/bin/view/Blog/DevPracticesByXWikiSAS
Leading a Community-Driven Open Source ProjectVincent Massol
Talk presented at Voxxed Luxembourg 2017.
This talk is a return of experience of 20 years developing open source software at the Apache Software Foundation (Jakarta Cactus, Apache Maven), at Codehaus (Cargo) and on the XWiki open source project (last 10 years).
Through the example of the XWiki open source project, the talk will tackle best practices and governance rules for running community-driven open source projects and it'll also tackle the difficult topic of how to run such a project when there are companies making money from the open source project behind the scene.
Examples of topics that will be covered:
* Committership
* Development best practices
* Roadmap definitions
* Fully automating software releases
* Handling companies
* Tracking who's using your project
Join the Java Evolution GIDS Bangalore & PuneHeather VanCura
The Java Community Process (JCP) is key to the evolution of Java technology. This session emphasizes the value of transparency and participation in the JCP program, through both Java User Groups (JUGs), and through the Adopt-a-JSR program, the grass roots, community led and developed program to empower Java developers around the world to make a contribution to Java technology. Find out how to become an active participant in advancing the Java platform - JSRs for Java Enterprise Edition (Java EE) 8 and Java Standard Edition (Java SE) 9 are being developed now. This session discusses the transparency that enables participation in the JCP program and how to get involved through the Adopt-a-JSR program. You will also hear about some upcoming changes to the Java Specification Request (JSR) process itself through the JCP.next effort, and learn how you can get involved. Come with your questions/suggestions, and leave with the motivation and information you need in order to become an active participant in advancing the Java platform now and in the future.
Crunching the numbers: Open Source Community Metrics at OSCONDawn Foster
Co-presented with Dave Neary at OSCON 2011.
Every community manager knows that community metrics are important, but how do you come up with a plan and figure out what you want to measure? Most community managers have their own set of hacky scripts for extracting data from various sources after they decide what metrics to track. There is no standardised Community Software Dashboard you can use to generate near-real-time stats on your community growth.
Like most open source projects, we have diverse community infrastructure for MeeGo, including Mailman, Drupal, Mediawiki, IRC, git, OpenSuse Build Service, Transifex and vBulletin. We wanted to unify these sources together, extract meaningful statistics from the data we had available to us, and present it to the user in a way that made it easy to see if the community was developing nicely or not.
Building on the work of Pentaho, Talend, MLStats, gitdm and a host of others, we built a generic and open source community dashboard for the MeeGo project, and integrated it into the website. The project was run in the open at http://wiki.meego.com/Metrics/Dashboard and all products of the project are available for reuse.
This presentation will cover the various metrics we wanted to measure, how we extracted the data from a diverse set of services to do it, and more importantly, how you can do it too.
Crunching the numbers: Open Source Community MetricsDawn Foster
Every community manager knows that community metrics are important, but how do you come up with a plan and figure out what you want to measure? Most community managers have their own set of hacky scripts for extracting data from various sources after they decide what metrics to track. There is no standardised Community Software Dashboard you can use to generate near-real-time stats on your community growth.
Like most open source projects, we have diverse community infrastructure for MeeGo, including Mailman, Drupal, Mediawiki, IRC, git, OpenSuse Build Service, Transifex and vBulletin. We wanted to unify these sources together, extract meaningful statistics from the data we had available to us, and present it to the user in a way that made it easy to see if the community was developing nicely or not.
Building on the work of Pentaho, Talend, MLStats, gitdm and a host of others, we built a generic and open source community dashboard for the MeeGo project, and integrated it into the website. The project was run in the open at http://wiki.meego.com/Metrics/Dashboard and all products of the project are available for reuse.
This presentation will cover the various metrics we wanted to measure, how we extracted the data from a diverse set of services to do it, and more importantly, how you can do it too.
This is an introduction to BiQ, the world's first SEO suite with granular cost control.
It incorporates details on who is BiQ, the story behind it, BiQ's mission statement, core principles and BiQ's key initiatives for the following stages.
For more information on this, head over to https://biq.cloud/
Lessons from Contributing to WebKit and BlinkBruno Abinader
Being one of the most successful open source projects to date, WebKit development process consists of a series of protocols and strict policies in order to obtain committer and reviewer status. Blink follows a similar approach with committers and scoped code owners, in a similar fashion as Linux Kernel does with its subsystem maintainers. Their open source success is due to not only solid support from major technology companies, but also to the high quality and automated testing performed on patches before submission. In this presentation, Bruno explains how the development process of both WebKit and Blink projects are - from submitting well-tested patches with strict policies to check, get review from community, and commit upstream via commit-queue system (including early warning system bots). This is a very practical talk with live demonstrations of patch submissions on both projects.
10 years have passed since the launch of Restlet Framework v1, the first RESTful API framework created, and thanks to our efforts and our open source community, we have gathered a lot of experience along the way. In parallel, the continuous innovation, competition and maturation in the web API space in general and in the Java space as well has created an opportunity to innovate again. The goal is to have a prototype of the v3 of the framework working, based on Netty and Reactive Streams, supporting HTTP/2 and async APIs in a RESTful way.
Presentation I gave at the OSSGTP meeting (http://ossgtp.org) about new stuff in XWiki Enterprise 2.0 and some of the things in store for the future.
See http://massol.myxwiki.org/xwiki/bin/view/Blog/XWikiEnterprise20AndFuture
Presentation Vincent Massol gave at the OSSGTP meeting (http://ossgtp.org) about new stuff in XWiki Enterprise 2.0 and some of the things in store for the future.
Internal training at [[XWiki SAS>>http://xwiki.com]] about the Development Practices used by the XWiki SAS product team in charge of developing the XWiki open source project (among other projects). Most of the practices detailed are those from the XWiki open source project, defined on the [[dev subwiki>>dev:Main.WebHome]]. However the slides also provide a glimpse of other development practices that are used to complement the open source practices, such as Roadmap preparation and Stakeholder meetings.
More details at http://www.xwiki.org/xwiki/bin/view/Blog/DevPracticesByXWikiSAS
Leading a Community-Driven Open Source ProjectVincent Massol
Talk presented at Voxxed Luxembourg 2017.
This talk is a return of experience of 20 years developing open source software at the Apache Software Foundation (Jakarta Cactus, Apache Maven), at Codehaus (Cargo) and on the XWiki open source project (last 10 years).
Through the example of the XWiki open source project, the talk will tackle best practices and governance rules for running community-driven open source projects and it'll also tackle the difficult topic of how to run such a project when there are companies making money from the open source project behind the scene.
Examples of topics that will be covered:
* Committership
* Development best practices
* Roadmap definitions
* Fully automating software releases
* Handling companies
* Tracking who's using your project
Join the Java Evolution GIDS Bangalore & PuneHeather VanCura
The Java Community Process (JCP) is key to the evolution of Java technology. This session emphasizes the value of transparency and participation in the JCP program, through both Java User Groups (JUGs), and through the Adopt-a-JSR program, the grass roots, community led and developed program to empower Java developers around the world to make a contribution to Java technology. Find out how to become an active participant in advancing the Java platform - JSRs for Java Enterprise Edition (Java EE) 8 and Java Standard Edition (Java SE) 9 are being developed now. This session discusses the transparency that enables participation in the JCP program and how to get involved through the Adopt-a-JSR program. You will also hear about some upcoming changes to the Java Specification Request (JSR) process itself through the JCP.next effort, and learn how you can get involved. Come with your questions/suggestions, and leave with the motivation and information you need in order to become an active participant in advancing the Java platform now and in the future.
Crunching the numbers: Open Source Community Metrics at OSCONDawn Foster
Co-presented with Dave Neary at OSCON 2011.
Every community manager knows that community metrics are important, but how do you come up with a plan and figure out what you want to measure? Most community managers have their own set of hacky scripts for extracting data from various sources after they decide what metrics to track. There is no standardised Community Software Dashboard you can use to generate near-real-time stats on your community growth.
Like most open source projects, we have diverse community infrastructure for MeeGo, including Mailman, Drupal, Mediawiki, IRC, git, OpenSuse Build Service, Transifex and vBulletin. We wanted to unify these sources together, extract meaningful statistics from the data we had available to us, and present it to the user in a way that made it easy to see if the community was developing nicely or not.
Building on the work of Pentaho, Talend, MLStats, gitdm and a host of others, we built a generic and open source community dashboard for the MeeGo project, and integrated it into the website. The project was run in the open at http://wiki.meego.com/Metrics/Dashboard and all products of the project are available for reuse.
This presentation will cover the various metrics we wanted to measure, how we extracted the data from a diverse set of services to do it, and more importantly, how you can do it too.
Crunching the numbers: Open Source Community MetricsDawn Foster
Every community manager knows that community metrics are important, but how do you come up with a plan and figure out what you want to measure? Most community managers have their own set of hacky scripts for extracting data from various sources after they decide what metrics to track. There is no standardised Community Software Dashboard you can use to generate near-real-time stats on your community growth.
Like most open source projects, we have diverse community infrastructure for MeeGo, including Mailman, Drupal, Mediawiki, IRC, git, OpenSuse Build Service, Transifex and vBulletin. We wanted to unify these sources together, extract meaningful statistics from the data we had available to us, and present it to the user in a way that made it easy to see if the community was developing nicely or not.
Building on the work of Pentaho, Talend, MLStats, gitdm and a host of others, we built a generic and open source community dashboard for the MeeGo project, and integrated it into the website. The project was run in the open at http://wiki.meego.com/Metrics/Dashboard and all products of the project are available for reuse.
This presentation will cover the various metrics we wanted to measure, how we extracted the data from a diverse set of services to do it, and more importantly, how you can do it too.
Platform - Depends on the size of the project and the type of its development, developers, and kind of platform.
Both the platforms Golang and Node.js were developed for different use & distinct purposes.
visit: https://www.forcebolt.com/
CON6423: Scalable JavaScript applications with Project NashornMichel Graciano
In the age of cloud computing and highly demanding systems, some new approaches for application architectures such as the event-driven model have been proposed and successfully implemented with Node.js. With the Nashorn JavaScript engine, it is possible to run JavaScript applications directly in the JVM, enabling access to the latest Node.js frameworks while taking advantage of the Java platform’s scalability, manageability, tools, and extensive collection of Java libraries and middleware. This session demonstrates how to use Nashorn to create highly scalable JavaScript applications leveraging the full power of the JVM by using the projects Avatar and Node.js with Avatar.js and Vert.x, highlighting their key benefits, issues, and challenges.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
AI Pilot Review: The World’s First Virtual Assistant Marketing SuiteGoogle
AI Pilot Review: The World’s First Virtual Assistant Marketing Suite
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-pilot-review/
AI Pilot Review: Key Features
✅Deploy AI expert bots in Any Niche With Just A Click
✅With one keyword, generate complete funnels, websites, landing pages, and more.
✅More than 85 AI features are included in the AI pilot.
✅No setup or configuration; use your voice (like Siri) to do whatever you want.
✅You Can Use AI Pilot To Create your version of AI Pilot And Charge People For It…
✅ZERO Manual Work With AI Pilot. Never write, Design, Or Code Again.
✅ZERO Limits On Features Or Usages
✅Use Our AI-powered Traffic To Get Hundreds Of Customers
✅No Complicated Setup: Get Up And Running In 2 Minutes
✅99.99% Up-Time Guaranteed
✅30 Days Money-Back Guarantee
✅ZERO Upfront Cost
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
Top 7 Unique WhatsApp API Benefits | Saudi ArabiaYara Milbes
Discover the transformative power of the WhatsApp API in our latest SlideShare presentation, "Top 7 Unique WhatsApp API Benefits." In today's fast-paced digital era, effective communication is crucial for both personal and professional success. Whether you're a small business looking to enhance customer interactions or an individual seeking seamless communication with loved ones, the WhatsApp API offers robust capabilities that can significantly elevate your experience.
In this presentation, we delve into the top 7 distinctive benefits of the WhatsApp API, provided by the leading WhatsApp API service provider in Saudi Arabia. Learn how to streamline customer support, automate notifications, leverage rich media messaging, run scalable marketing campaigns, integrate secure payments, synchronize with CRM systems, and ensure enhanced security and privacy.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
2. About XWiki
●
Web platform on top of
the wiki paradigm
●
Structured data, scripting,
applications
●
Java platform, polyglot
applications (JSR223)
●
XWiki Enterprise – the
product
●
LGPL license, since 2004
●
www.xwiki.org
3. XWiki Features
● Modular and highly extensible
●
Version control, attachments, user and rights
management, subwiki and subpages,
comments, wiki syntax and WYSIWYG editor,
macros, notifications, skins, search,
import/export, apps, etc.
● Use cases:
● Knowledge sharing and collaboration
● Intranets, knowledge base, public websites,
groupware, education, etc.
5. Community
● Users, Contributors and Core committers
●
Core and Contrib
●
Meritocracy
●
Governed by committers
● New committers voted based on contribution
● Lazy consensus
●
Important changes go through voting
●
+1, +/-0, -1
● Core committers have veto (-1) rights
6. Roadmap and Releases
● Timeboxing vs Feature-driven
●
Open roadmap for each minor release
●
1 major release per year
●
Minor releases (2.5 months)
● Dev releases (1-3 weeks)
● Bugfix releases
●
Support 3 versions (Dev, Stable & LTS)
● Release Manager Roster (taking turns)
●
Release Process on xwiki.org
19. Dev Principles
● High focus on quality
● dev.xwiki.org dedicated to dev documentation and
best practices
●
Enforcing coding style and min. test coverage
●
XWiki special days (Bug Fixing Days, etc.)
●
High focus on backwards compatibility
● Deprecation strategy
● Legacy modules
23. Earning a living
● Multiple companies build their businesses on
top of XWiki
● XWiki.com is the main company sponsoring the
development of the project (since 2004)
● Professional Support
●
Consulting & Training
● Custom Development & Solutions
●
Hosting
●
Sustainable alternative to proprietary
Applications: Apache Velocity + JSR223: Python, Groovy, JavaScript, PHP, Ruby, etc.
Internal (scripting) and external APIs for CRUD data operations.
Open Development, not just open Source
Frequent releases = Early feedback
No single Release Manager + documented process = low bus factor
Users, devs, contributors
Users, Devs, Notifications (central)
- roadmap discussions
- ask for help
- votes, proposals, announcements
- BFDs
- asynchronous
- publicly indexed by (3+) services and searchable by google
- also has a forum-like view with nabble
Alternative: forum
- needs account, need to go on the forum to interact (even if notified by mail), etc.
Synchronous discussions
IRC Bot (XWiki) Application on xwiki.org
- wiki modifs and code commits live notifications
- Jira link completion
- chat archive
Freenode.org for OS projects and interractions
Open, standard and well known protocol that already has (and is easy to add) many integrations even if maybe less sexy
OSS license
- Dashboards, filters, reports
- Used in Roadmap tracking
- more powerful than github issues
- we started with Jira, hard to move away
Contributors can assign and close issues
- issues closed by PRs have proper assignee
Core + Contrib exts
GitHub integration
We do not close older issues
Mandatory documentation and release notes fields checked by the release process
GitHub – the place to be, social, etc.
xwiki & xwiki-contrib organizations
Pull Requests
Many code reviews for core, less picky for contrib extensions
Cvs, svn, git (Hub)
Alternative: Bitbucket
- not interested in Mercurial or private repos
We store at least 3 branches for all supported versions
3 set of builds, 1 for each supported vers.
Full integration, snapshots, up to distrib
- unit tests, integration/functional tests for each module (minimal test instance)
- security, web/accessibiltity standards
- performance
- quality (fails build if coverage not me + reports)
- sonar metrics
Screenshot of failing UI tests (even for older builds)
See what commit breaks build
Incremental builds on commit, full builds on manual trigger
Quality level analysis
- coverage, metrics, best practices, severity levels, architecture/design issues, etc.
- technical debt
- gives you a place to start when you want to improve something
OSS License
Proxy multiple repos
+ maven.xwiki.org/releases /externals /snapshots
Core + Contrib exts
Allows extensions to depend on each other and distributions to package extensions
Used by maven builds of individual modules (without needing to rebuild everything)
Product even if the result, is still connected to the project's infrastructure, even after it's installed and running (through EM/DW)
Updates and new extensions from e.x.o (repository/index)
- actually downloaded from either e.x.o or nexus.xwiki.org (if in core or contrib)
Repo index + extension documentation
Admin, install, config, high-level doc on xwiki.org + blog
dev.xwiki.org – dev doc, best practices, etc.
Translations
Eating our own dogfood, various use cases of Xwiki (KB, App store, translation tool, etc.)
Free to edit, monitored on IRC live and on mail (digests/watchlist)
IntelliJ: OSS licenses
Open by default
Going open source is not an anti-pattern for a business
Having a business contribute to a project helps the project overall